←
Revnet | Tokenize your revenues and fundraises374 posts
Revnet | Tokenize your revenues and fundraises avatar

Revnet | Tokenize your revenues and fundraises

@revnets

An investible business model for the open web. REV collects revenues from ecosystem activity, see the REV revnet at revnet.money/eth:3

◷ Joined December 2023▧ 11 Photos and videos
jango.eth avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
jango.eth@me_jango·Nov 8

Here's my email to galsterdam@ethreum.org describing @juiceboxETH and @revnets Glam implications. Hi, We simulated Juicebox V6 against Glamsterdam (EIP-8037/8038) on Sepolia chains (Ethereum, Base, Optimism, Arbitrum). The pattern to watch is a fail-open try/catch around an external call. With a tuned gas limit, the callee can run out of gas while the outer call succeeds and treats that as an ordinary failure. BACKGROUND Under EIP-150, each call level keeps 1/64 of its gas. When a deep call runs out, the levels above revert and hand that gas back. Spent gas is gone, but the outer call can finish on what was never spent. Contracts can forward less, but can't turn this off. This happens on mainnet today, and contracts can be tuned to today's gas constraints so these accidental revert-then-continues don't happen. If the constraints change, so does the execution, and immutable contracts can't follow. WHAT GLAMSTERDAM CHANGES Two changes can let the outer call finish where it couldn't before: 1. New slots go from about 22k to about 98k gas, which mostly hits callees, not the work after a catch. 2. State gas spent by a reverting frame can return mid-transaction, which can't happen today. FINDING 1: OP STACK L1 MESSENGER (NOT OUR CODE) L1CrossDomainMessenger reserves 40k gas to record a failed relay, which is less than a new slot now costs. If the target runs out of gas, the failure may go unrecorded. The portal finalizes the withdrawal with no replay, and the ETH stays in the L1 bridge. github.com/ethereum-optimism… Our first L2 to L1 root is lost at 1.06M to 2.00M gas on OP and 1.02M to 1.97M on Base. Our 375k message limit is too low, and an unbuffered eth_estimateGas hit that range. With an all-gas-burning target, it's lost up to 7.7M. Ethereum mainnet records the failure from about 960k. github.com/Bananapus/nana-su… These contracts are on L1, so exposure starts when L1 activates Glamsterdam, whether or not the L2s adopt it. We haven't contacted OP or Base yet. FINDINGS 2 TO 5: JUICEBOX V6 Our core and hook try/catch calls set no gas limit or reserve, so they keep only the 1/64. The native-token paths below showed no window on the mainnets we swept, because their callees were too cheap to starve. All of them have a window on Glamsterdam Sepolia. 2. Payouts: anyone can call sendPayoutsOf. At 878k to 1.03M gas, a split to another project fails, the transaction succeeds, and the money returns to the project with the payout limit used. On mainnet, a simple test hook needs 3.2M+ gas. Routed token splits weren't swept. github.com/Bananapus/nana-co… 3. NFTs: at 2.85M to 3.11M gas, a buyer keeps the NFT while the tier's split payment fails. The recipient gets nothing, the money goes to the project instead, and there's no retry. github.com/Bananapus/nana-72… 4. Reserved tokens: at 488k to 815k gas, a split meant to pay another project fails, so the beneficiary gets the raw tokens instead. The destination project never receives the payment. github.com/Bananapus/nana-co… 5. Fees: at 678k to 819k gas, the 2.5% cash-out fee call fails and the fee is forgiven. The holder's reclaim doesn't change, and the fee stays in the project as fee-free surplus. github.com/Bananapus/nana-co… METHOD We used eth_simulateV1 on fresh test projects, so real projects will differ. The bridge test used the real portal with an overridden proof and a synthetic message. Nothing was sent on Sepolia. The messenger cause is inferred from the code and the numbers, not traced. QUESTION Fail-open try/catch assumes a callee with a reasonable gas budget won't starve. If the parent can finish after the callee runs out of gas, the caller chooses the outcome. Our V6 contracts are immutable, so a fix means redeploying. In practice, the latest version of the protocol, deployed in June, currently holds about $140k, all of which looses its value prop given a faulty protocol under Glam. The greater threat is the uncertainty Glam creates for protocol clients going forward. It's impossible to trust an immutable protocol like Juicebox and Revnets if failures caused by changes to the underlying network are fair game. Earlier versions of the protocol have facilitated over $200m of ETH volume, including for significant moments like ConstitutionDAO, AssangeDAO and the Tornado Cash legal defense fund. Those versions no longer facilitate new projects, but they carry Glamsterdam risks similar to V6's. What is our course of action? We can share the simulation scripts and the exact eth_simulateV1 requests if they'd help. Thanks, Jango Juicebox

Bruhva. I’ve read this. Less passive aggressive way to respond would be just to affirm the email is in fact the best way… and best service would be to translate the twitter postings into formal tickets for me. Same team. I’ll send the email.

Markee avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
Markee@markee_xyz·Sep 1

Today we deployed For Rent Markee signs, launching a new open marketplace for digital attention. Built to be the most fun way you can monetize your web space. Modeled after Harberger Taxes, using best-in-class payments infra: @revnets @Superfluid_HQ @ethereum @base

Post attachment
jango.eth avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
jango.eth@me_jango·Jun 30

1) move revenue directly to token holders. 2) minimize/remove governance. 3) step away and let the engine go brr. revnets

jango.eth avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
jango.eth@me_jango·Apr 23

MEV guy reached out, we got the 21 mainnet ETH back. What luck. Thank you.

Last week, @ESultanik from @trailofbits reported to me an exploit in @revnets found by @AnthropicAI. All Revnet V5 funds were at risk. Sunday i attempted a whitehat rescue of the funds. I successfully pulled $140k of funds belonging to the @Artizen ART revnet and @markee_xyz MARKEE revnet. In the process, I lost ~25 mainnet ETH from the NANA @juiceboxETH, REV @revnets, and BAN @bannynet revnets... due to my negligence in executing the script. MEV got the best of my urgency in the heat of the moment, despite thinking I did all I could to be ready to go. All other non-revnet Juicebox projects are unaffected. For the past three months, I have been working on an "AI hardened" version of Juicebox – a fork of V5 that has gone through the ringer of any and all AI, harness, any novel auditing concept I could get my hands on. This weekend's exploit took advantage of a nuance in the revnet loans code that I had caught and fixed at the beginning of this process, but I had not realized it put funds at risk until reported by TOB and Anthropic. I'm grateful we managed to keep customers' funds safe, and regretful we'll have to start our own businesses over. I'm frustrated at myself for having left the exploit in the original code, and for failing to recover all of it despite the opportunity. I'm encouraged knowing I've already been working on the solution and won't be starting this AI risk assessment from 0... the downtime will be relatively short. But most of all I'm relieved that this AI security moment has come now, when funds at risk were relatively modest. I do not envy those with centi-million dollar protocols in production going into 2026. Despite doing all we could to get the Juicebox and Revnet V4/5 protocols audited over the past three years before deploy, the obsessive manual reviews and tests from ourselves and from top pros still missed what the latest AI crawlers have caught. The other side of this diligence storm is sunny. This turbulence is a blessed precondition for open finance, one that will level up the quality of open source, enable anyone to run audits, and allow those of us who take responsibility over the integrity of these public tools to sleep better at night. We must get to the other side. As usual, I will continue running my businesses using my own tools that I do everything to derisk, and I will continue telling others that they probably shouldn't follow my lead – the tradeoffs are real and borne by users of the open source. But I've found there are folks like me who stubbornly prefer assuming this risk if the reward is the freedom, agency, and strong guarantees the tools offer in their ideal form, unlike the corporate landscape of law-fare, capture, and executive discretion. Reaching the ideal form is inevitable if we keep going at it. It is the holy grail. Open source, open accounting, and the open internet can and will outcompete everything, but damn the journey ain't easy. On a practical note: V5 NANA, REV, and BAN holders will receive their V6 tokens as soon as the protocol is deployed, and we will restart revenue aggregation from there. MARKEE and ART holder will also receive their V6 tokens, and have their whitehat rescued funds added to their revnets to back the value of the tokens. These next few weeks before we launch V6, we need all hands on deck pointing AIs at it and fishing for exploit opportunities, efficiency nudges, documentation clarification, and everything in between. JBX and REV rewards to those who report issues. All you have to do is pull up Claude Code, Codex, or your favorite LLM and run: "Clone github Bananapus/version-6 recursively, read AUDIT_INSTRUCTIONS.md, then walk me through my options for auditing this codebase. Ask me how deep I want to go, which subsystem interests me, and whether I have any specialization to add — then start."

jango.eth avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
jango.eth@me_jango·Apr 21

Last week, @ESultanik from @trailofbits reported to me an exploit in @revnets found by @AnthropicAI. All Revnet V5 funds were at risk. Sunday i attempted a whitehat rescue of the funds. I successfully pulled $140k of funds belonging to the @Artizen ART revnet and @markee_xyz MARKEE revnet. In the process, I lost ~25 mainnet ETH from the NANA @juiceboxETH, REV @revnets, and BAN @bannynet revnets... due to my negligence in executing the script. MEV got the best of my urgency in the heat of the moment, despite thinking I did all I could to be ready to go. All other non-revnet Juicebox projects are unaffected. For the past three months, I have been working on an "AI hardened" version of Juicebox – a fork of V5 that has gone through the ringer of any and all AI, harness, any novel auditing concept I could get my hands on. This weekend's exploit took advantage of a nuance in the revnet loans code that I had caught and fixed at the beginning of this process, but I had not realized it put funds at risk until reported by TOB and Anthropic. I'm grateful we managed to keep customers' funds safe, and regretful we'll have to start our own businesses over. I'm frustrated at myself for having left the exploit in the original code, and for failing to recover all of it despite the opportunity. I'm encouraged knowing I've already been working on the solution and won't be starting this AI risk assessment from 0... the downtime will be relatively short. But most of all I'm relieved that this AI security moment has come now, when funds at risk were relatively modest. I do not envy those with centi-million dollar protocols in production going into 2026. Despite doing all we could to get the Juicebox and Revnet V4/5 protocols audited over the past three years before deploy, the obsessive manual reviews and tests from ourselves and from top pros still missed what the latest AI crawlers have caught. The other side of this diligence storm is sunny. This turbulence is a blessed precondition for open finance, one that will level up the quality of open source, enable anyone to run audits, and allow those of us who take responsibility over the integrity of these public tools to sleep better at night. We must get to the other side. As usual, I will continue running my businesses using my own tools that I do everything to derisk, and I will continue telling others that they probably shouldn't follow my lead – the tradeoffs are real and borne by users of the open source. But I've found there are folks like me who stubbornly prefer assuming this risk if the reward is the freedom, agency, and strong guarantees the tools offer in their ideal form, unlike the corporate landscape of law-fare, capture, and executive discretion. Reaching the ideal form is inevitable if we keep going at it. It is the holy grail. Open source, open accounting, and the open internet can and will outcompete everything, but damn the journey ain't easy. On a practical note: V5 NANA, REV, and BAN holders will receive their V6 tokens as soon as the protocol is deployed, and we will restart revenue aggregation from there. MARKEE and ART holder will also receive their V6 tokens, and have their whitehat rescued funds added to their revnets to back the value of the tokens. These next few weeks before we launch V6, we need all hands on deck pointing AIs at it and fishing for exploit opportunities, efficiency nudges, documentation clarification, and everything in between. JBX and REV rewards to those who report issues. All you have to do is pull up Claude Code, Codex, or your favorite LLM and run: "Clone github Bananapus/version-6 recursively, read AUDIT_INSTRUCTIONS.md, then walk me through my options for auditing this codebase. Ask me how deep I want to go, which subsystem interests me, and whether I have any specialization to add — then start."

jango.eth avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
jango.eth@me_jango·Apr 21

Yall, please help secure upcoming Juicebox V6. Open a Claude/Codex terminal tab and run: "Clone github Bananapus/version-6 recursively, read AUDIT_INSTRUCTIONS.md, then walk me through my options for auditing this codebase. Ask me how deep I want to go, which subsystem interests me, and whether I have any specialization to add — then start." it'll ask you a few questions about how much effort you want to through at the audit, and then auto submit issues to the repo. Huge help.

Gitcoin avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
Gitcoin@gitcoin·Mar 12

🔒 Deploy a treasury once. Fund your project forever. No grants committee, no governance vote, no owners. That's the core claim behind @revnets: autonomous revenue networks built on @juiceboxETH and powered by immutable rules onchain. It's one of the more radical experiments in the funding landscape right now, and it raises a real question: can code do the job we've always needed human judgment to do? Probably ↓ 🔗 gitcoin.co/research/revnets-…

Markee avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
Markee@markee_xyz·Mar 2

Superfluid's Markee message uses our Leaderboard Pricing Strategy🥇 Here's how it works: ▸ Minimum 0.003 ETH to buy a message ▸ The message with the most funds gets the Top Spot ▸ Add funds to any existing message to move it up the Leaderboard ▸ 62% of funds go to Superfluid's treasury, 38% goes to the Markee Cooperative, which issues MARKEE tokens on @revnets ▸ You own your message. Edit it anytime at markee.xyz/ecosystem/superfl…

There's a sign on the internet and right now someone called stemo.eth is paying to keep their message at the top of it. That's @markee_xyz in a nutshell and it’s powered by Superfluid 🌊 Here's how it works ↷

Post attachment
paul 🪧 avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
paul 🪧@Paul_Glavin·Mar 3

All this is possible with pricing strategies! The smart contract for the message itself is outrageously simple: basically just holds a text string + pricing strategy and routes funding to @revnets All the logic determining how much the user pays, when that text string is changed, etc are handled in the strategy contract, which is interchangeable and infinitely composable. Could definitely include things like time locks & message queues. I’ve thought about e.g. having a version of @NegationGame as a pricing strategy to optimize for quality / purpose of the message, not just top-bidder-wins. Lots of really cool stuff you can do.

Kai Micah Mills avatar
⟳ Revnet | Tokenize your revenues and fundraises retweeted
Kai Micah Mills@kaimicahmills·Feb 5

the long-awaited paper showing structural preservation of a human cryopreservation patient’s brain from greg fahy et al is out we can see clearly identifiable synapses, intact membranes, and no evidence of ice damage, even after years in liquid nitrogen storage 🧊🧠

Post attachment