A subgraph is right until the protocol ships again.
What a protocol ships after launch:
- New contracts
- New versions of old ones
- New formulas for the same number
What each release asks of the index:
- Notice the release
- Index the new contracts
- Check the new figures against the contract
When The Standard Reserve (@standard_rsv) launched new contracts, we were indexing them within hours and we dedicated and upgraded our index and APIs once a week for the last 6 weeks.
Protocol by protocol, iteration by iteration.
Talk to us about Flex: onesource.io/solutions/flex-…
When a protocol launches, participants have questions right away. Buy a license now or wait? How long until a branch pays back?
For The Standard Reserve (@standard_rsv), our dashboard and API were serving live data about 90 minutes before the public mint opened.
Read about how we got the data ready here: onesource.io/blog/standard-r…
Welcome to the world of KYA (know-your-agent).
Humans have already decided they will be turning over more and more of their actions (and decisions) to agents. There's no putting Pandora back in the box.
What's needed from here is enabling agents to work with banks and brokerages in a compliant, authorized way.
This is where the tokenization economy will have a distinct advantage. As assets are tokenized and transacted onchain, you can gain access to robust access control, auditing, and governance tools.
This is why we built Aegis. We see a world in which agents will need better guardrails and permissions to be embraced by onchain and tradfi finance alike.
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios.
The findings have alarmed banking executives, who are racing to restrict access to their systems as AI moves at a velocity faster than financial institutions can respond, multiple industry and bank executives told Axios.
Several banks are now preparing for worst-case and even “day after” scenarios, including how to rapidly secure or restore customer accounts if things go wrong, the people said.
Several bank executives told Axios they're struggling to distinguish between human users and AI agents. One executive said banks also struggle to determine whether agents are authorized by customers or potentially operating without their permission, more akin to rogue agent behavior.
Read my latest for Axios here: axios.com/2026/10/22/ai-agen…
Agent-driven finance is where blockchains will win.
Permissions or "policies" can be baked in and enforced directly in the smart contracts, ensuring that valid operations can proceed.
Add in audit logs and white listed apps/protocols, and you can have a full end-to-end life cycle of what an Ethereum wallet can and can't do with user funds.
This is available today with Aegis projectaegis.ai.
Where should an agent's payment rules live?
In the prompt:
- The agent reads them
- A prompt injection can rewrite them
In your app:
- Your code checks them
- Only if every payment goes through that code
In the account:
- The chain checks them before the transaction executes
Aegis puts the rules in the account:
- Allowlisted actions, tokens, protocols, and chains
- Spend limits and time windows
- Transaction counts
Outside the policy? It reverts.
Live on Base. Free during early access: projectaegis.ai
The Standard Reserve continues to evolve. Here's how we've updated our coverage of @standard_rsv at tsr.onesource.io and api.onesource.io.
Own a charter? There's a new one-time stimulus: 1M STANDARD for charters, plus an 89.5k top-up, claimable until Nov 10. Enter your wallet at tsr.onesource.io/decide/wall… to see what each of your charters can still claim. So far 390 wallets have claimed about 833k from the main pool, and our claimed totals match both stimulus contracts' own on-chain counts.
Thinking of a full exit? It burns the charter, and a burned charter can't claim, so any unclaimed stimulus is lost. tsr.onesource.io/decide/exit now shows how much you'd give up. We confirmed it by simulating an exit followed by a claim.
The new launchpad pays charters too. When a launch token graduates, it can set aside a share for charter holders, paid for each branch a charter closes after that. tsr.onesource.io/decide/wall… shows what you can claim from each of the 18 drops so far, /decide/exit shows what closing branches would release, and /decide/branch shows what one branch has earned. We checked every charter in every drop against the contract's own numbers: 18,657 checks, all matching.
One catch: closing a charter's last branch burns it, and a burned charter can only claim drops if its owner was recorded on the drop contract first. The wallet page shows that status for each charter.
The expansion vault moved most of its ETH into Uniswap v4 positions, USDG and stock tokens. Counting ETH alone would miss most of the reserve, so backing at tsr.onesource.io/protocol/su… now counts all of it at current pool prices.
For agents: /v1/wallets/{address}, /v1/charters/{id}, /v1/decisions/exit, /v1/decisions/branch, /v1/supply/current and /v1/backing/current in the API, or the matching 1s_std_* tools in npmjs.com/package/@one-sourc… (5.23.1).
Monetary Policy Update: Charter Stimulus and Branch Reductions
Standard has been incredibly efficient at bringing tokens back into the protocol. Burns are far outpacing issuance and nearly $1M has been deployed into buybacks and ETH-side liquidity.
With the upcoming launchpad and liquidity pools, Standard continues to build toward its larger vision.
While market conditions and activity on Robinhood Chain are outside the protocol's control, issuance appears to be heading toward another cut to 0.2×, the floor. This is the mechanism working as intended, tightening emissions when market activity slows.
However, the protocol's efficiency has allowed it to accumulate a significant surplus of STANDARD through POL fees, putting it in a unique position to support long-term Charter holders despite broader market conditions.
As part of this issuance cut, the number of branches available per auction will be reduced to 25, further slowing the growth of future issuance.
To reward that long-term commitment, the protocol will also distribute a portion of its accumulated surplus as a one time bonus to eligible existing branches, bringing their payout to the equivalent of approximately 0.7× issuance for that distribution.
Eligibility will be limited to Charters that have purchased at least one branch through open-market auctions, demonstrating long-term commitment to the protocol. Claim is live on the site's announcements.
The issuance multiplier will still fall to 0.2× and every token distributed will come from what the protocol has already earned.
Everyone is building a spend cap for AI agents this month. Examples:
* Hackathon team, because Razorpay's SDK, MCP server, and CLI have no concept of a spend cap for an agent (their words)
* A Reddit builder, with a policy + authorization layer between intent and signature ("I don't want a $100 approval to silently become a $101 approval")
* Mastercard, with Agent Pay checks that run before authorization
* Nvidia, with a hardware watchdog that quarantines an agent that leaves its boundaries
So from individual hackathon participants to one of the biggest AI companies in the world, everyone is interested around authorization limits!
The good news: Aegis already does this, on chain, with the guidelines you choose:
* Spend limits, time windows, transaction counts
* Allowlisted tokens, protocols, chains
* Enforced inside the transaction's validation step
* Outside the policy? It reverts.
Aegis is now live on Base. Free during early access.
Save yourself the hackathon (and the headache): projectaegis.ai/
Claim: In the AI-era, blockchain protocols need rapidly evolving intelligence.
Evidence: Standard Researve launched on X, and we were able to wrap an intelligence layer around their newly minted contracts within hours (see tsr.onesource.io)
But that was just the start!
Unlike previous crypto cycles (where new features were shipped quarterly or monthly), Standard Reserve was able to fast-follow with their launch with multiple significant releases (within weeks, sometimes day).
Examples:
* v1.1 preserved the retired license auction's sales next to the replacement contract's history.
* v1.2 showed the live charter auction as it runs, bids, fills, and cancellations are indexed; and S-Bills, with the exit fee estimated for any amount before you stake.
OneSource detected and upgraded its intelligence layer with each release.
The new meta isn't just to empower users protocol by protocol, but iteration by iteration.
Are you looking to provide your protocol users with up to date APIs and MCP servers? DM us for more information.
A fixed amount, to one approved address, on a set schedule. That's the whole payroll promise.
Keeping an autonomous agent to that promise is the hard part. One bad prompt and it can send funds nobody approved.
Aegis closes that door by coding spending rules directly into the wallet. Wrong amount, wrong recipient, the transaction just doesn't go through.
The best version of payroll is the one you don't think about. Everyone gets paid, nothing goes wrong, and you don't hear a thing about it.
Here's how we built it: onesource.io/blog/aegis-smar…
We've added more ways to look at @standard_rsv on frontend at tsr.onesource.io and via our API at api.onesource.io.
Want out of an S-Bill early? Enter the bill ID at tsr.onesource.io/decide/sbil…. You'll see the exit fee today and for every day until the bill matures. We checked it against the contract's own exit quote on all 218 open bills, and the numbers match.
Bidding on a license? tsr.onesource.io/decide/bid shows when the auction price will reach your max and how many bids are ahead of yours. The full book is at tsr.onesource.io/protocol/au….
Thinking of selling? tsr.onesource.io/decide/exit now shows what the same STANDARD would earn if you staked it in an S-Bill instead.
The expansion vault moved into a 2-of-4 multhere and counts both its ETH and its USDG.Both numbers match the vault's on-chain balance.
/v1/flows/protocol shows where the protocol's money goes: tax forwards, buybacks, fee collection, liquidity pairing, team claims and transfers out of the vault.
Some of the contracts' events never had a published signature. We matched the hashes ourselves, so every event now shows up by name.
For agents: /v1/decisions/sbill, /v1/decisions/bid and /v1/flows/protocol in the API, or the matching 1s_std_* tools in npmjs.com/package/@one-sourc… (5.23.0).
We've updated our @standard_rsv frontend (tsr.onesource.io) and API (api.onesource.io) for S-Bills, the protocol's new fixed-term staking.
Now you can see what you'd lock in before you stake. Enter an amount at tsr.onesource.io/decide/stak… for the rate per term, the premium you'd earn at maturity, and the fee if you left right away.
Leaving early currently costs 2% to 15% of principal, depending on how much has left S-Bills in the past week. We estimate that fee for any amount. Our estimate currently matches the contract's own quote on all 94 open bills. You can check any bill at /v1/sbills/bills/{id}.
Every bill, with its rate and maturity, is at tsr.onesource.io/protocol/sb…. Enter an address at /decide/wallet to see what it has staked.
The S-Bill contract's source code isn't public. We read its interface from the deployed code and checked every event against the chain before indexing it.
Feed the data to your agent with /v1/sbills/* in the API or 1s_std_sbills_* tools in @ one-source/mcp 5.22.0.
OneSource retweeted
GM.
It’s a strong ‘Manufacturing Monday’. 🇺🇸
The latest ISM data shows U.S. manufacturing expanding for the ninth consecutive month.
September Manufacturing PMI: 54.5
New Orders: 55.3
Production: 56.7
Employment: 52.7
Backlog of Orders: 51.1
Prices: 77.9
Five of the six largest manufacturing industries expanded during the month.
But more manufacturing also means more materials, suppliers, testing, certifications and documentation moving through increasingly complex supply chains.
As manufacturing scales, so does the need to establish what a product is, where its inputs came from, whether requirements were met and whether the evidence supporting those claims can be trusted.
Manufacturing capacity matters.
So does the integrity of the data behind it.
Most of the agent-payments conversation is still about capability:
* Can an agent hold a wallet? Credit card?
* Can it pay per call? API key?
* Can it settle in stablecoins?
The industry has largely answered these with multiple solutions for each.
The question beyond them is still wide open. CAN and SHOULD should we trust an agent with a wallet in the first place?
The common answer so far? A slow, after-the-fact process.
* Log the transaction.
* Alert human.
* Fix and reconcile (if possible).
That works at human speed, which is no longer acceptable in an era where thousands of agent swarms are attacking Huffing Face (and, soon, other apps and protocols).
The alternative is to bind the authority BEFORE the agent acts!
This can be done with a policy written and enforced on the chain during the execution path.
Outside the policy? The transaction reverts. Here's the key point...
There is nothing to review because there is nothing to undo.
That is what we built Aegis for. Spending and usage guardrails for both sides, buyers and merchants, checked where the transaction happens rather than in a dashboard after the fact.
Get started today at projectaegis.ai/
We've updated our @standard_rsv frontend (tsr.onesource.io) and API (api.onesource.io) for S-Bills, the protocol's new fixed-term staking.
Now you can see what you'd lock in before you stake. Enter an amount at tsr.onesource.io/decide/stak… for the rate per term, the premium you'd earn at maturity, and the fee if you left right away.
Leaving early currently costs 2% to 15% of principal, depending on how much has left S-Bills in the past week. We estimate that fee for any amount. Our estimate currently matches the contract's own quote on all 94 open bills. You can check any bill at /v1/sbills/bills/{id}.
Every bill, with its rate and maturity, is at tsr.onesource.io/protocol/sb…. Enter an address at /decide/wallet to see what it has staked.
The S-Bill contract's source code isn't public. We read its interface from the deployed code and checked every event against the chain before indexing it.
Feed the data to your agent with /v1/sbills/* in the API or 1s_std_sbills_* tools in @ one-source/mcp 5.22.0.
Giving an AI agent a wallet is the easy half.
The questions people keep arriving at...
1. How much economic authority are you willing to delegate?
2. What happens the first time the agent is wrong?
3. How much $$ are you willing to put at risk given 1 and 2?
The key issue: being able to complete a purchase is not the same as having the authority to make it!
Attack Vectors:
* An honest mistake in prompt
* Malicious prompt injection
* Bad data source
* Bug in the code
* Weak spending limits
All of this becomes a problem in dynamic markets at machine speeds!
Approval after the fact is not a control.
This is why Aegis puts necessary constraints in the execution path.
* Write a policy.
* Bind the agent to it.
* The chain enforces it before the transaction.
* Outside the policy, it reverts.
Live in beta. Link below to get started.
projectaegis.ai/
Give an AI agent a budget and it'll find ways to spend it efficiently.
Sounds good, until you realize "efficiently" is the agent's call, not yours.
And there's usually no way to catch a bad decision before the transaction's already settled.
Aegis enforces spending rules at the point of transaction, not after.
We walked through exactly how, using a live Venice AI integration: onesource.io/blog/control-ai…
We've updated our @standard_rsv frontend (tsr.onesource.io) and API (api.onesource.io) for protocol v1.2.
Now you can see the charter auction as it runs: today's price, when the next day opens, what each past day closed at, and whether a license or a charter is the cheaper way to open a branch right now. tsr.onesource.io/decide/char… and /v1/auctions/*.
v1.2 also added auto-bidding to the license auction. Bids, fills and cancellations are indexed, and a filled bid counts as one sale.
Both auctions moved to new contracts in v1.2. We now read their addresses from the protocol's own AddressRegistry on every run, so the next move is picked up automatically. If the registry and our data ever disagree, /v1/data-health says so, and tsr.onesource.io/protocol/go… shows every registry address.
Sales history carries across all three LicenseAuction generations, and the retired contracts stay in the contract directory so earlier purchases remain attributable.
Protocol v1.2 upgrade is here.
1. Limit orders for branch auctions. Users can now place bids at their desired auction price. It is an open orderbook and execution price is FCFS best attempt by a keeper.
2. Charter auctions begin. There will be 1 charter auctioned at the same cadence as the branch auctions. The first charter auction starts at 5.5 ETH and will open at 3x clearing price for the following auctions.
All changes have gone through a security review.
When new protocols launch onchain, there is often a steep learning curve to use them.
Well, what about using an AI agent?
This is still a big challenge because they can't make decisions and take actions on data that's not available.
Worse, what if they pick the wrong contract and get scammed?
This is where OneSource Flex shines. We can quickly easily index verified contracts and use them to power dashboards, APIs, MCPs, and anything else humans and agents need to use these protocols.
Checkout our recent example with @deepstatesh, a novel DEX native to Robinhood chain: onesource.io/blog/robinhood-…
We've updated our Deepstate @deepstatesh indexers, API and MCP tools to be DGP-3 compliant.
New routes /v1/token/2deep and /v1/migration track supply and redemption progress, and one-source/mcp 5.20.0 adds 1s_ds_token_2deep and 1s_ds_migration.
The same data can be found via our frontend at deepstate.onesource.io.
Introducing $2DEEP.
One token for Deepstate governance and rewards, bringing $DEEP and $STATE together.
deepstate.sh/govern/dgp-3
We’ve updated our @standard_rsv frontend (tsr.onesource.io) and API (api.onesource.io) for protocol v1.1.
/v1/vaults/* and /v1/backing/* now report incentives_vault_std_raw - the STANDARD balance held in the new incentives vault, where v1.1 forwards POL buybacks.
We also preserved sales from the retired LicenseAuction alongside the replacement contract’s history, surfaced the new twice-daily auction cadence, and aligned license-cap calculations with the new auction windows.
Other updates include charter-holder flow analytics at /v1/flow/charters, exact exit-fee expiry schedules, richer auction-day aggregates, and improved supply and decision dashboards.
Protocol v1.1 updates go live today. There are 3 specific changes:
1. There are 2 license auctions a day, 12H durations at 50 branches each. There is still a limit of 3 branches per 24H per charter.
2. Faster price curves, auction half life is now 2H.
3. Bid-side only POL. The POL vault used to pair both ETH and token side liquidity. It will now only pair bid side liquidity by buying tokens off the market and sending those tokens to a new protocol owned incentives vault.
All changes have gone through a security review.
