{ Want to stake your SOL with Raiku? }
- It takes less than a minute.
- Here's how.
↓
Visit stake.raiku.com
1. Connect your Solana wallet.
2. Enter the amount of SOL you want to stake.
3. Click Deposit and approve the transaction.
4. Receive rkuSOL instantly.
Step 2
- Join the Raiku Discord.
- Go to the connect wallet channel.
- Click Verify rkuSOL Holdings.
- The bot will generate your private account page along with a unique security code.
- Always make sure the code matches before connecting anything.
↓
Step 3
- On your Raiku Account page, connect:
- Discord
- X
- Solana Wallet
[ Once all three are linked, your rkuSOL balance is verified automatically ]
That's it.
↓
Why should you do this?
> your wallet becomes linked to your community identity.
> your rkuSOL holdings are verified.
> You're recognized as an rkuSOL holder inside the Raiku ecosystem.
> It takes less than two minutes
> Small effort
Big step toward becoming an active member of the Raiku community
@raikucom@duckk9x@ZhugeLyang@mrahsok@_offmylawn
{ People ask me how I spot projects worth paying attention to }
- I don't start with the timeline
- I start with the capital
- 127K+ SOL is already staked in solana:rkubjTrZYioRSeXwDnhwGQzvW3qkcin72JSxUt3WMVp
- 899 holders.
- 1 rkuSOL = 1.00940 SOL.
- That isn't just a number
[ It's conviction from people willing to lock their assets behind Raiku's vision ]
Worth keeping on your radar
{ so there are actually two different execution problems here }
- and i think this distinction is pretty important
- one is
"i know exactly when this transaction needs to happen"
the other is
"i don't know when it will happen, but when the trigger comes i need it immediately"
- these sound similar
- but they're completely different situations
- take a fund rebalancing at quarter end
- or a scheduled coupon payment
- or a settlement with a hard deadline
- you know the timing beforehand
- you don't need to race anyone
- you need to book the slot
- that's where AOT comes in
Ahead of Time execution lets you reserve a specific future block
you choose the slot
submit a sealed bid
and if you win, you get a signed confirmation before the transaction executes
now compare that with a liquidation
the position crosses the threshold
and suddenly you need the transaction to happen
right now
you can't schedule that event ten seconds earlier because you didn't know when the trigger would happen
that's where JIT comes in
Just in Time gives the transaction priority access to the next available block when the trigger fires
so basically
AOT is for planned certainty
JIT is for reactive certainty
same problem at a higher level
but two very different ways of solving it
Jumper has officially announced the solana:Aybt5BWuW6kMNt7Jk1UmSgLzpEKev5pEnh82TA5rpump Token Sale.
• Sale starts 29th Sep
• Sale FDV: $75M
• 50% unlocked at TGE
• Remaining 50% unlocks linearly over 4 months
• $3M total raise
To get access, you need either:
• A strong Legion Score
• Top 500 position on the Jumper waitlist
You can still join the waitlist here:waitlist.jumper.xyz/r/JMP-BB…
The important part is referrals.
Don’t just focus on quantity. Bringing active and quality X accounts can help you move up the leaderboard.
Personally, I think solana:Aybt5BWuW6kMNt7Jk1UmSgLzpEKev5pEnh82TA5rpump will be an interesting one to watch after launch.
Could this be a 2x to 4x from the sale valuation?
What’s your Legion Score?
If you've ever built anything in crypto, you know the data problem gets complicated pretty quickly.
One API for market data.
Another for onchain data.
Another for wallets.
Another for news.
Then another one for prediction markets.
You end up spending more time connecting data than building the actual product.
That's where Surf API comes in.
Surf is trying to bring all of that into one data layer.
One key.
One format.
90+ endpoints.
The coverage is pretty broad too.
Onchain SQL across 7 chains.
100M+ labeled addresses across 13 networks.
Live prediction market data from both Polymarket and Kalshi.
Cross market matching.
934M+ rows of trade history.
And market data with pre computed indicators already available.
There is also Surf Skill for AI agents.
It lets Claude Code and Cursor query Surf's CLI natively, so you don't have to hardcode every schema yourself.
Surf also has 80+ analyst ready onchain tables covering things like DEX trades, token transfers, TVL, lending, staking and bridges.
And the agents can automatically discover the table schemas.
For builders, that's an important detail.
Because the goal isn't just to have more data.
It's to make that data easier for an AI agent to actually use.
Instead of stitching together 5 to 10 different APIs, you can work through one system.
That's the builder side of Surf.
Tomorrow, I'll cover some of the smaller Surf updates that make the research experience much smoother.
@SurfAIHQ
Crypto research usually starts with a project name.
You see it in a post.
Someone mentions it in a group chat.
Or it suddenly starts trending.
Then the real question is:
What is actually going on with this project?
That's where Cryptopedia comes in.
Surf has a library of 23,000+ crypto projects.
But it's not just a list of projects.
You can look into things like onchain activity, funding history, tokenomics, team information, DeFi metrics and airdrop status.
The useful part is that this information is cross referenced with live data.
So instead of only reading what a project's website or marketing says, you can check what the numbers actually look like.
Who funded it?
What's happening onchain?
How does the tokenomics look?
What is the current DeFi activity?
That makes Cryptopedia more useful as a starting point for research.
Then there's Crypto Pulse.
Think of it as Surf's live Web3 news feed.
It pulls news from 30+ sources including The Block, CoinDesk, Cointelegraph, Decrypt and Blockworks.
The stories are AI classified by sentiment and relevance, so you can quickly see whether something is being classified as bullish, bearish or neutral.
There's also Surf AI News, which provides original market briefs from Surf's own analysts.
The idea is pretty simple.
Cryptopedia helps you understand the project.
Crypto Pulse helps you understand what's happening around the market.
And both sit on top of the same Surf data layer.
Tomorrow, I'll get into the builder side of Surf again.
Surf API and Skill.
@Surfdeveloper
Crypto research usually starts with a project name.
You see it in a post.
Someone mentions it in a group chat.
Or it suddenly starts trending.
Then the real question is:
What is actually going on with this project?
That's where Cryptopedia comes in.
Surf has a library of 23,000+ crypto projects.
But it's not just a list of projects.
You can look into things like onchain activity, funding history, tokenomics, team information, DeFi metrics and airdrop status.
The useful part is that this information is cross referenced with live data.
So instead of only reading what a project's website or marketing says, you can check what the numbers actually look like.
Who funded it?
What's happening onchain?
How does the tokenomics look?
What is the current DeFi activity?
That makes Cryptopedia more useful as a starting point for research.
Then there's Crypto Pulse.
Think of it as Surf's live Web3 news feed.
It pulls news from 30+ sources including The Block, CoinDesk, Cointelegraph, Decrypt and Blockworks.
The stories are AI classified by sentiment and relevance, so you can quickly see whether something is being classified as bullish, bearish or neutral.
There's also Surf AI News, which provides original market briefs from Surf's own analysts.
The idea is pretty simple.
Cryptopedia helps you understand the project.
Crypto Pulse helps you understand what's happening around the market.
And both sit on top of the same Surf data layer.
Tomorrow, I'll get into the builder side of Surf again.
Surf API and Skill.
@Surfdeveloper
{ this is probably the Surf product I find most interesting }
> Surf Chat helps you research.
> Surf Studio lets you build.
> The idea is pretty simple.
You describe what you want, and Studio turns it into a working web app connected to Surf’s live data.
For example:
“Build me a whale alert dashboard.”
Or:
“Create a Polymarket vs Kalshi arb scanner.”
You don’t need to start by writing code.
You describe the idea, Studio builds it, then you can preview it, tweak it and deploy it to a live URL.
The interesting part is what’s already connected underneath.
~ Prices.
~ Wallets.
~ Onchain data.
~ Prediction markets.
So you’re not building a frontend and then spending hours figuring out how to connect different APIs.
Studio already works with Surf’s data layer.
And the Build Challenge gave a pretty good idea of what people are actually doing with it.
819 builders showed up.
1,234 apps were deployed.
582 were submitted to the gallery.
All within two weeks.
People built cycle top indicators, wallet scanners, airdrop tools, trading dashboards and more.
One of the winners, TopSignal, combined 12 onchain and cycle indicators with live risk scoring and trading posture recommendations.
Another built a wallet analyzer that looked for forgotten tokens, dormant positions and unclaimed assets.
And the KOL Shill Analyzer compared token calls against actual price performance.
What I like here is that these weren’t just random demos.
People were building around problems they already had.
That’s probably the biggest idea behind Studio.
You don’t have to wait until you know how to build everything yourself.
You can start with the problem.
Then build around it.
The Build Challenge is over, but Studio is still there.
And every submission lives in the Studio Gallery, where you can browse, use and remix them.
Tomorrow, I’ll get into Cryptopedia and how Surf approaches researching the 23,000+ projects in its database.
@Surfdeveloper
{ so what exactly is this }
"engineering contract"
that Raiku keeps talking about?
it's not an actual legal contract
( it's basically the set of promises a blockchain makes through its architecture )
- how transactions get ordered
- how quickly they settle
- how reliably they land
and what happens when the network is under pressure
when an institution puts capital onchain
it's accepting all of those rules
> that's the engineering contract
> and Solana already has some pretty strong parts here
> sub second finality
> high throughput
> low costs
these are real properties
and they're a big reason institutions are coming to Solana
but then you get to execution certainty
and things become a little different
Solana doesn't guarantee that your transaction lands in a specific block
it doesn't separate time critical transactions from normal traffic
and priority fees don't really change that underlying structure
you can pay more
but you're still competing for the same blockspace
that's fine for a lot of onchain activity
but institutional finance has a different standard
they need to know what the commitment is before the trade happens
and what happens if that commitment isn't met
that's the part of the engineering contract Raiku is trying to change
[ i think there's a part of Solana that institutions care about which doesn't get talked about enough ]
it's not really speed anymore
- Solana is already fast
- cheap
- and has strong finality
{ that's a big reason institutional capital is coming onchain in the first place }
but there's a difference between
"this transaction usually lands quickly"
and
"i know exactly when this transaction will land"
for a retail swap, maybe that difference isn't a big deal
but for a fund with a specific mandate
a scheduled settlement
or a trade that needs to happen at a particular moment
it matters a lot
because institutions don't really operate on
"hopefully"
they need commitments they can understand before the transaction happens
and that's where the current Solana model starts showing a gap
- you can pay priority fees
- you can compete harder for blockspace
- but you still aren't booking a specific block in advance
- that's basically the problem @raikucom is trying to solve
not by making Solana faster
but by adding more certainty around when execution actually happens
and imo
that's a pretty important piece if Solana wants to handle the next wave of institutional capital
{ this is probably the Surf product I find most interesting }
> Surf Chat helps you research.
> Surf Studio lets you build.
> The idea is pretty simple.
You describe what you want, and Studio turns it into a working web app connected to Surf’s live data.
For example:
“Build me a whale alert dashboard.”
Or:
“Create a Polymarket vs Kalshi arb scanner.”
You don’t need to start by writing code.
You describe the idea, Studio builds it, then you can preview it, tweak it and deploy it to a live URL.
The interesting part is what’s already connected underneath.
~ Prices.
~ Wallets.
~ Onchain data.
~ Prediction markets.
So you’re not building a frontend and then spending hours figuring out how to connect different APIs.
Studio already works with Surf’s data layer.
And the Build Challenge gave a pretty good idea of what people are actually doing with it.
819 builders showed up.
1,234 apps were deployed.
582 were submitted to the gallery.
All within two weeks.
People built cycle top indicators, wallet scanners, airdrop tools, trading dashboards and more.
One of the winners, TopSignal, combined 12 onchain and cycle indicators with live risk scoring and trading posture recommendations.
Another built a wallet analyzer that looked for forgotten tokens, dormant positions and unclaimed assets.
And the KOL Shill Analyzer compared token calls against actual price performance.
What I like here is that these weren’t just random demos.
People were building around problems they already had.
That’s probably the biggest idea behind Studio.
You don’t have to wait until you know how to build everything yourself.
You can start with the problem.
Then build around it.
The Build Challenge is over, but Studio is still there.
And every submission lives in the Studio Gallery, where you can browse, use and remix them.
Tomorrow, I’ll get into Cryptopedia and how Surf approaches researching the 23,000+ projects in its database.
@Surfdeveloper
{ i used to think Surf Chat was basically another AI tool for asking crypto questions }
it is a lot more useful than that.
The main difference is the data behind the answers.
Surf Chat can pull from all 12 data domains at the same time, so you can ask questions that normally require jumping between multiple tools.
For example:
- Want to check EigenLayer's funding history?
- It can combine project research with VC data.
- Want to see ETH whale activity from the last 24 hours?
- It can use wallet tracking and address intelligence.
- Want to compare Arbitrum and Base DEX volume over the last 30 days?
That's where Surf's onchain SQL comes in.
This is the part that makes it interesting for actual crypto research.
The problem isn't usually finding one piece of information.
> It's connecting everything together.
> Price data from one place.
> Wallets somewhere else.
> Onchain activity somewhere else.
> Funding data somewhere else.
> News and narratives somewhere else.
By the time you've checked everything, you've already spent 30 minutes.
Surf is trying to turn that into one conversation.
And they've been adding some useful research features around it too.
You can paste a YouTube video and ask questions about it.
Upload a whitepaper, CSV, image or document.
Highlight a specific part of a research report and ask a follow up without rewriting the whole context.
You can even ask for technical indicators like RSI, MACD, EMA200, Bollinger Bands or Fibonacci and have them drawn directly on the chart.
So the interesting part isn't really "AI answers crypto questions."
It's that Surf can connect the question to live crypto data.
Less tab switching.
More actual research.
Tomorrow, I'll get into Surf Studio, which takes the same data layer and lets you build apps with it.
@Surfdeveloper
{ so what exactly is this }
“engineering contract”
that Raiku keeps talking about?
it’s not an actual legal contract
it’s basically the set of promises a blockchain makes through its architecture
how transactions get ordered
how quickly they settle
how reliably they land
and what happens when the network is under pressure
when an institution puts capital onchain
it’s accepting all of those rules
that’s the engineering contract
and Solana already has some pretty strong parts here
sub second finality
high throughput
low costs
these are real properties
and they’re a big reason institutions are coming to Solana
but then you get to execution certainty
and things become a little different
Solana doesn’t guarantee that your transaction lands in a specific block
it doesn’t separate time critical transactions from normal traffic
and priority fees don’t really change that underlying structure
you can pay more
but you’re still competing for the same blockspace
that’s fine for a lot of onchain activity
but institutional finance has a different standard
they need to know what the commitment is before the trade happens
and what happens if that commitment isn’t met
that’s the part of the engineering contract @raikucom aiku is trying to change
[ i think there's a part of Solana that institutions care about which doesn't get talked about enough ]
it's not really speed anymore
- Solana is already fast
- cheap
- and has strong finality
{ that's a big reason institutional capital is coming onchain in the first place }
but there's a difference between
"this transaction usually lands quickly"
and
"i know exactly when this transaction will land"
for a retail swap, maybe that difference isn't a big deal
but for a fund with a specific mandate
a scheduled settlement
or a trade that needs to happen at a particular moment
it matters a lot
because institutions don't really operate on
"hopefully"
they need commitments they can understand before the transaction happens
and that's where the current Solana model starts showing a gap
- you can pay priority fees
- you can compete harder for blockspace
- but you still aren't booking a specific block in advance
- that's basically the problem @raikucom is trying to solve
not by making Solana faster
but by adding more certainty around when execution actually happens
and imo
that's a pretty important piece if Solana wants to handle the next wave of institutional capital
Most protocols try to create incentives around their token.
@standard_rsv is taking a different approach.
Instead of asking:
“How do we make people hold $STANDARD?”
The system is designed around a much bigger question:
“What should a monetary system do when capital enters or leaves?”
——————————————
That’s where Standard Reserve by @0xbeans gets interesting.
The protocol has one main market where ETH and $STANDARD interact.
Every epoch, Standard looks at the actual ETH moving through that market.
More ETH entering the system means expansion.
More ETH leaving means contraction.
That single signal influences how the monetary system behaves.
——————————————
Now look at what happens to the people participating in the system.
You enter through a Charter.
Your Charter gives you Branches.
Branches determine your share of newly issued $STANDARD.
Want more Branches?
You need to buy an expansion license using $STANDARD.
And those tokens don’t go back into circulation.
They are burned.
So the same mechanism that lets participants increase their share can also reduce the circulating supply.
——————————————
The supply design is another important part.
$STANDARD has a maximum supply of 1 billion.
Only 100 million starts as protocol owned liquidity.
The remaining issuance is controlled by the monetary system and isn’t simply released all at once.
At the same time, tokens can continuously leave circulation through licenses, buybacks and other burns.
So supply isn’t just about printing.
It’s also about how much the system removes.
——————————————
And then there is the reserve side.
When conditions are positive, protocol fees can accumulate toward hard reserves such as tokenized gold and permanent liquidity.
When conditions turn negative, the same fee engine can support market buybacks and burns.
So the revenue isn’t designed to depend on only one market direction.
Expansion has a destination.
Contraction has a response.
——————————————
Even exits have their own economic design.
A Branch has to be retired when you withdraw its accumulated earnings.
And when system wide withdrawals become heavy, the resolution fee increases.
Half of that fee is burned.
The other half goes to the bankers who remain.
It creates an interesting dynamic:
Leaving during normal conditions is one thing.
Leaving while everyone else is rushing out is another.
——————————————
There are only 1,000 Genesis Charters.
And Standard is still very early.
So I’m less interested in simply asking how valuable the Charter NFT could become.
I’m more interested in whether these mechanisms can actually create a sustainable onchain monetary economy.
Because if the design works as intended, Standard isn’t just another token protocol.
It’s an experiment in building a bank where monetary policy, reserves, incentives and exits are all controlled by code.
Something worth watching closely. 👀
{ i used to think Surf Chat was basically another AI tool for asking crypto questions }
it is a lot more useful than that.
The main difference is the data behind the answers.
Surf Chat can pull from all 12 data domains at the same time, so you can ask questions that normally require jumping between multiple tools.
For example:
- Want to check EigenLayer's funding history?
- It can combine project research with VC data.
- Want to see ETH whale activity from the last 24 hours?
- It can use wallet tracking and address intelligence.
- Want to compare Arbitrum and Base DEX volume over the last 30 days?
That's where Surf's onchain SQL comes in.
This is the part that makes it interesting for actual crypto research.
The problem isn't usually finding one piece of information.
> It's connecting everything together.
> Price data from one place.
> Wallets somewhere else.
> Onchain activity somewhere else.
> Funding data somewhere else.
> News and narratives somewhere else.
By the time you've checked everything, you've already spent 30 minutes.
Surf is trying to turn that into one conversation.
And they've been adding some useful research features around it too.
You can paste a YouTube video and ask questions about it.
Upload a whitepaper, CSV, image or document.
Highlight a specific part of a research report and ask a follow up without rewriting the whole context.
You can even ask for technical indicators like RSI, MACD, EMA200, Bollinger Bands or Fibonacci and have them drawn directly on the chart.
So the interesting part isn't really "AI answers crypto questions."
It's that Surf can connect the question to live crypto data.
Less tab switching.
More actual research.
Tomorrow, I'll get into Surf Studio, which takes the same data layer and lets you build apps with it.
@Surfdeveloper
{ i think most people are using Surf for just one thing }
and that's probably the biggest mistake.
Surf isn't just a crypto AI chatbot.
It's a full crypto AI agent platform built around one shared data layer.
- 12 data domains.
- 23,000+ crypto projects.
- 7 blockchains.
- And five products are built on top of it:
- Surf Chat
- Surf Studio
- Cryptopedia
- Crypto Pulse
- Surf API
The interesting part is that they all work from the same underlying data.
Market data with real time prices from 16 exchanges, plus indicators like RSI, MACD, Bollinger Bands, NUPL, SOPR and MVRV.
80+ analyst ready onchain SQL tables covering things like DEX trades, transfers, TVL, lending, staking and bridges.
Wallet profiling across multiple chains, including DeFi positions and transaction history.
100M+ labeled addresses across 13 networks, where you can get actual identities instead of seeing another random wallet address.
Prediction market data from both Polymarket and Kalshi, with 934M+ rows of trade data.
Funding and VC data from seed through Series C.
And AI classified news from 30+ sources.
That's a lot of data sitting underneath the products.
But the important part isn't the number.
It's what you can actually do with it.
You can research something in Surf Chat.
Turn that research into an app with Studio.
Verify a project through Cryptopedia.
Follow what is happening through Crypto Pulse.
Or connect the data directly to your own AI agent through the API.
Same foundation.
Different ways to use it.
Over the next 7 days, I'll break down each part of Surf and what I think is actually worth paying attention to.
Starting tomorrow with Surf Chat.
@Surfdeveloper
{ i think most people are using Surf for just one thing }
and that's probably the biggest mistake.
Surf isn't just a crypto AI chatbot.
It's a full crypto AI agent platform built around one shared data layer.
- 12 data domains.
- 23,000+ crypto projects.
- 7 blockchains.
- And five products are built on top of it:
- Surf Chat
- Surf Studio
- Cryptopedia
- Crypto Pulse
- Surf API
The interesting part is that they all work from the same underlying data.
Market data with real time prices from 16 exchanges, plus indicators like RSI, MACD, Bollinger Bands, NUPL, SOPR and MVRV.
80+ analyst ready onchain SQL tables covering things like DEX trades, transfers, TVL, lending, staking and bridges.
Wallet profiling across multiple chains, including DeFi positions and transaction history.
100M+ labeled addresses across 13 networks, where you can get actual identities instead of seeing another random wallet address.
Prediction market data from both Polymarket and Kalshi, with 934M+ rows of trade data.
Funding and VC data from seed through Series C.
And AI classified news from 30+ sources.
That's a lot of data sitting underneath the products.
But the important part isn't the number.
It's what you can actually do with it.
You can research something in Surf Chat.
Turn that research into an app with Studio.
Verify a project through Cryptopedia.
Follow what is happening through Crypto Pulse.
Or connect the data directly to your own AI agent through the API.
Same foundation.
Different ways to use it.
Over the next 7 days, I'll break down each part of Surf and what I think is actually worth paying attention to.
Starting tomorrow with Surf Chat.
@Surfdeveloper
[ i think there's a part of Solana that institutions care about which doesn't get talked about enough ]
it's not really speed anymore
- Solana is already fast
- cheap
- and has strong finality
{ that's a big reason institutional capital is coming onchain in the first place }
but there's a difference between
"this transaction usually lands quickly"
and
"i know exactly when this transaction will land"
for a retail swap, maybe that difference isn't a big deal
but for a fund with a specific mandate
a scheduled settlement
or a trade that needs to happen at a particular moment
it matters a lot
because institutions don't really operate on
"hopefully"
they need commitments they can understand before the transaction happens
and that's where the current Solana model starts showing a gap
- you can pay priority fees
- you can compete harder for blockspace
- but you still aren't booking a specific block in advance
- that's basically the problem @raikucom is trying to solve
not by making Solana faster
but by adding more certainty around when execution actually happens
and imo
that's a pretty important piece if Solana wants to handle the next wave of institutional capital
{ so if AOT lets you reserve a future slot }
the next question is
how do you actually decide what that blockspace is worth?
that's where the marketplace comes in
@raikucom treats Solana blockspace as compute units
and obviously, not every user needs the same thing
somebody doing a liquidation might need execution right now
while an institution might already know exactly when it needs to settle
so instead of forcing everyone into the same execution model
Raiku has two pricing paths
JIT
for immediate execution
AOT
for future delivery
JIT uses a first price sealed bid auction
while AOT uses an open English style auction where users bid against each other for specific future slots
and i think the AOT part is especially interesting
because if you know ahead of time when you need blockspace
you can actually plan your execution around it
rather than showing up at the last second and competing for whatever is available
> basically
> urgent execution gets one market
> planned execution gets another
> same blockspace
> different needs
{ so if AOT lets you reserve a future slot }
the next question is
how do you actually decide what that blockspace is worth?
that's where the marketplace comes in
@raikucom treats Solana blockspace as compute units
and obviously, not every user needs the same thing
somebody doing a liquidation might need execution right now
while an institution might already know exactly when it needs to settle
so instead of forcing everyone into the same execution model
Raiku has two pricing paths
JIT
for immediate execution
AOT
for future delivery
JIT uses a first price sealed bid auction
while AOT uses an open English style auction where users bid against each other for specific future slots
and i think the AOT part is especially interesting
because if you know ahead of time when you need blockspace
you can actually plan your execution around it
rather than showing up at the last second and competing for whatever is available
> basically
> urgent execution gets one market
> planned execution gets another
> same blockspace
> different needs
[ one thing i found interesting about AOT ]
- is that you’re not reserving an entire block
- you’re reserving compute units inside that block
- that might sound like a small detail
- but it’s actually pretty important
- at the beginning of every epoch
validators decide what percentage of their blockspace they want to make available for AOT reservations
builders can then bid for that reserved compute through Raiku
but here’s the clever part
if that reserved blockspace doesn’t get sold
or the winner doesn’t end up using it
it doesn’t just sit there doing nothing
it goes right back to processing normal transactions
so validators aren’t wasting capacity
and regular users aren’t being blocked because someone reserved space they never used
i think that’s a pretty practical design
you’re creating a market for future blockspace
without taking useful blockspace away from everyone else
@raikucom
{ so if JIT is all about }
“i need this transaction in the next slot”
then what happens when you already know exactly when your transaction needs to execute?
( that’s where AOT comes in )
- Ahead of Time transactions are almost the opposite of JIT
- instead of competing for the next available slot
- you’re reserving blockspace for a specific future slot
- think about things like
> institutional settlement windows
> scheduled oracle updates
> vault rebalancing
> batch processing
> repaying a loan before a deadline
none of these need to happen immediately
they just need to happen at the right time
and that’s an important difference
because today, even if you know your transaction needs to execute at 14:03 UTC…
you still have to wait until 14:03
submit it
and hope everything goes smoothly
with AOT, the planning happens before that
you reserve the blockspace ahead of time
then when that slot arrives
your transaction is already expected to land there
i think that’s a pretty different way of looking at blockspace
not just as something you compete for
but something you can actually plan around