Portable Intent in a Cast

Most people don’t think about MIME types (Multipurpose Internet Mail Extensions). .jpg, .mp4, .pdf they just work. But behind every file, every upload, every tap to open, sits a three decade old standard that started life in a strange place: email attachments.

MIME was invented so we could send pictures and documents through early email systems. Then the web adopted it, browsers leaned on it, and suddenly MIME types were the invisible grammar of the internet. Every click we have made since — from TikTok to Spotify — has been orchestrated by this silent taxonomy.

I still remember in 3rd grade asking, “Can I go to the bathroom?” and Ms. Patterson correcting me: “I’m sure you can, but may you?” That was my first lesson in how grammar quietly governs what is allowed and what is not. MIME works the same way. We rarely notice it, but it has been policing the boundaries of digital possibility for decades.

But here is the catch: MIME types have always been about static, inert formats. .jpg means “this is an image,” .mp3 means “this is audio.” Great for the web of documents, but what about the web we are entering now?

Think about the media that defines today. It is not just articles or videos. It is miniapps inside a feed. It is agents managing your picks, simulations running fantasy what ifs, retro cards that are part image, part stat line, part onchain mint or offchain attestation.

The old MIME types were enough for email and for ads. But they do not capture this new medium of actions.

• A cast that is not just text, but also a button to buy a ticket
• An agent that carries not only memory but also a wallet
• A simulation that does not just play back, but branches forward into alternate auditable futures

If MIME types were the grammar of the early web, what I'll refer to as Capsules are starting to look like the vocabulary of the next one.

They are not just ways to describe files, they are ways to describe what media can do. Actions packaged up, ready to move through feeds, chats, and apps.

To make that concrete, here is a first sketch of what a new Capsule family could look like.

📦 Capsule Family

.sim → Simulation Capsule

A replayable world, not just a recording.
Example: Replay EPL Game Week 2 but swap the starting lineup; simulate a Footy App treasury payout under different rules.
How it works: Runs like a sandboxed engine where rules and states can be reloaded and changed.
Analogy: Like a video game save file you can load and play differently each time.

.agt → Agent Capsule

Portable memory, personality, and actions in a file.
Example: Drop in a commentator agent to narrate the match highlights, or a Footy App bot that tracks your fantasy roster and nudges you before kickoff.
How it works: Encodes traits, skills, and memory in a portable container that can be called anywhere.
Analogy: Like carrying around a Pokémon card that can come alive and act for you.

.rev → Reversion Capsule

Timelines you can rewind and fork forward.
Example: Roll back a fantasy trade decision and branch into alternate outcomes; fork a Footy App treasury split to see who would get paid under different settings.
How it works: Stores past states and branching paths so you can roll back and play out alternatives.
Analogy: Like a time machine remote for your season.

.ken → Knowledge Capsule

Structured, portable context an agent can instantly load.
Example: EPL Season pack with fixtures, results, and embeddings; a shard of fantasy scoring rules so your agent instantly knows football.
How it works: Holds schema, context, and embeddings in a compact portable file.
Analogy: Like a flash drive for knowledge — plug it into any agent and it speaks the game.

.trv → Traversal Capsule

Maps of paths and journeys through data or networks.
Example: Trace a Farcaster conversation graph backward to kickoff, then branch forward through match day banter.
How it works: Encodes pathways and steps so agents or users can traverse networks of data.
Analogy: Like a questline map — you pick which path to walk, not which world to run.

.mix → Hybrid Capsule

Bundle of text, image, code, and contract ABIs in one.
Example: A Footy App retro card that is part PNG, part JSON stats, part tokenURI metadata — media and mint fused.
How it works: Wraps multiple formats and execution hooks into a single bundle.
Analogy: Like a magic backpack holding different tools, all accessible at once.

.pay → Payment Capsule

Crypto native value transfer tucked inside media.

Example: A cast that carries a prize payout or ticket split inline — no checkout, no detour.

How it works:

• The host app's wallet is the signer — the actor that says “yes, send this”
• The blockchain is the settlement layer — the shared ledger where the payment lands
• The Capsule is the container — it carries the payment intent inside the cast, making it portable anywhere

Analogy: Like an envelope with cash inside — except it travels with the message itself, ready to be opened and settled with a tap, not after the fact.

A Glimpse Forward

The first MIME era gave us the web of documents.
The second MIME era gave us the web of ads.
The next era is shaping into the web of agents and actions.

Imagine this: it is match day, Liverpool are playing Newcastle. In your Footy App feed a friend drops a cast with a retro card. But it is not just an image — it is a .mix Capsule. You tap and see stats, a button to mint, and an inline .pay Capsule where you toss in 0.001 ETH for the prize pool. At halftime, an .agt Capsule drops — Peter Drury’s AI twin narrating the highlights. After the match, a .sim Capsule lets you rerun the game: what if the subs were different, what if Gordon did not see red or if Konate did.

When I say feeds where media is not inert, it is alive I mean that posts will stop being just representations of something, like a picture of the game or a clip of a goal, and start being containers of action.

A Capsule is not just attached to a message like an old email file or a link embed. It is the message on the snapchain.

• A .sim Capsule does not just show highlights — it lets you rerun the match with different lineups
• A .pay Capsule does not just link to a checkout page — it carries the payment inside the cast
• A .ken Capsule does not just describe stats — it gives your agent the knowledge of the season in a single drop

That is why I think of them as intents made portable.
They are not passive files or url embeds to be opened later in a miniapp, they are actions, ready to run, wherever they travel.

And if MIME was the grammar of the web we inherited, Capsules might just be the playbook of the one we are building.

🎶 You $BETR You $BETR You bet 🎶

You betr, you betr, you bet, ooh

You better, you better, you bet, ooh

You better, you better, you bet, ooh

You better, you better, you bet, ooh

I call you on the blockchain node
My gas too high with ETH regrets
I sometimes feel I should just go home
But I’m chasing that memecoin pump that never forgets

I love to hear you shill my name
Especially when you ape yes
Got your wallet right now on my mind
But I rugged myself blind to the sound of old DEXs
Mmm
To the sound of old DEXs
Oh, and who’s next?

When I say, “I hodl,” you say, you $BETR
You better, you better, you $BETR
When I say, “I need moon,” you say, you $BETR
You better, you better, you $BETR

You better bet your life
Or FUD will cut you like a knife

I want those paper-handed axes overthrown
I’m not into your KYC picture
I just like your chrome (Ledger cold)
You welcome me with diamond hands & open bags
I know only fools degen trades
But this one never lags

I don’t really mind how much you pump me
Ooh, a little’s alright
When you say, “Come over & stake tonight
Tonight, tonight”

When I say, “I hodl,” you say, you $BETR

You better, you better, you $BETR

When I say, “I need moon,” you say, you $BETR

You better, you better, you $BETR

You betr bet your life
Or FOMO cuts you, cuts you like a knife

For all the Terms of token issuance, splits, allocations, and exist rules check out https://www.revnet.app/base:53

Buying through Footy App issues tokens to you and sends a split of tokens to the core team. The ETH from your purchase backs the token supply. The core rules are onchain and cannot be changed.

Holders can borrow or sell anytime — there’s always liquidity. Revnet has a cash-out UX and might offer better prices than a DEX, though integration into Footy App hasn’t been a priority yet. There’s also an exit tax — leaving rewards those who stay by increasing their token value.

In theory, with perfect information (yeah right), the swap price in your wallet wouldn’t go above issuance price or below the floor — with some corner-case exceptions. Over time, arbitrage bots will make pricing more efficient.

Why a liquidity pool? To get $SCORES into the hands of football fans. @noiceapp distributes via likes, replies, and recasts — a highly targeted approach compared to other farmable tactics. The only way to get a token into that app is to have a DEX liquidity pool. I’ve thought about removing the tiny liquidity or adding more, but for now it’s staying put to see if someone spots an opportunity.

For now, the focus is on building and creating offerings that generate fees and demand for $SCORES, then distributing and raising awareness through @noiceapp and other Farcaster-native tactics that tightly target fans of the beautiful game.

$SCORES Flywheel

1. Fans play games using $SCORES, with some ETH flowing into the treasury to back $SCORES
2. Demand for $SCORES grows as fans use it in play and unlock offerings
3. Purchases send a portion of tokens to the core team
4. Team borrows against $SCORES to fund ops & rewards
5. New offerings & rewards attract more players
6. Backing per token increases, raising the floor price
7. Stronger token value drives more demand & participation

The Need for an Inflation‑Protected Asset

Inflation can quietly erode the value of your money, and sometimes not so quietly. In 2022, U.S. consumer prices spiked by 9.1% year-over-year – the highest jump in 40 years. Even after aggressive Fed action, inflation was still about 3% for 2024, above the historical 2% target. In practical terms, $1 in your wallet today buys less than $1 did a year ago, and over time that loss compounds.

Traditional finance offers TIPS (Treasury Inflation-Protected Securities) to combat this – bonds indexed to inflation to protect investors’ purchasing power. TIPS increase their principal with the Consumer Price Index so that your payout grows with rising prices.

Inspired by this idea, the crypto world may ask: Can we create a DeFi native token that also offsets inflation, preserving (or even growing) real value? Not some wrapped so called Real World Asset. Let's not only play a different game, let's create a new sport! How about $TIPS, an inflation-resistant RevNet token designed to do just that.

What are $TIPS?

$TIPS (named after those inflation-indexed bonds🤔) is a new concept: an inflation-resistant token launched as a RevNet. If you haven’t heard of Revnets, think of them in this context as an unowned, automated “vending machine” contracts with rules set in stone from day one. You put in some base asset and get a project token out; later, you can put the token back in to redeem value, all according to predefined immutable rules – no greedy 'trusted' admins or DAO votes needed.

In the case of $TIPS, you’ll deposit USDC and mint $TIPS tokens. The twist: the token’s issuance and redemption follow a curve designed to reward long-term holding and moderate dilution, so the effective value of $TIPS is designed to rise over time.

Now, let's be clear: $TIPS isn’t pegged to CPI or any live inflation oracle. This isn’t a synthetic CPI tracker or a Fed-reactive asset. It’s inspired by the goalsof TIPS, but more like a crypto-native variable rate Certificate of Deposit (CD). Rules are set up front. It follows a predetermined tapering schedule and bonding curve redemption logic. Over time, if you hold through the taper and let others exit early, the backing per token increases.

So call it TIPS meets variable rate CD, served via Revnet.

Backed by USDC: A Stable Foundation

$TIPS is 100% backed by USDC, providing a stable denominator for its value. Why USDC? Because if we’re offsetting inflation, we want a stable unit (the U.S. dollar) as the baseline. USDC is a widely used, dollar-pegged stablecoin, so 1 USDC ≈ $1. By backing $TIPS with USDC, we ensure that each $TIPS token is redeemable for some amount of real USD value at any time.

Unlike algorithms or volatile crypto collateral, USDC backing keeps $TIPS grounded – one foot firmly in stable value, while the token’s structure handles the long-term growth logic. This setup means no wild price swings unrelated to macro reality; $TIPS’s value relative to USDC evolves from issuance and redemption mechanics, not hype.

Issuance Taper: Quarterly Adjustments for Steady Growth

Every quarter—timed to the real-world financial rhythm of the FOMC—the issuance rate of $TIPS drops. Think of it like bitcoin halvings but more regular and pre-set. Early holders get more tokens per USDC contributed, but that window closes fast.

We should explore taper frequencies:

• Daily Taper: Highly responsive tiny increase that is probably too twitchy but sure would be intersteing.
• Monthly Taper: Highly responsive but potentially too twitchy.
• Quarterly Taper: Matches macro cadence. Good balance of pace and simplicity.
• Annual Taper: Simple, but too slow for dynamic inflation expectations and building energy in the Revnet.

Quarterly might hit the sweet spot to start as it gives the protocol breathing room and keeps issuance in sync with user behavior. But here's the thing—this isn't a monolith. Anyone can launch their own $TIPS Revnet with different taper parameters. You could have a monthly $TIPS, an annual one, or even something wilder. Let the market experiment.

Each version will diverge. That’s the point.

Fair Launch Principles: No Pre‑Mine, No Special Reserves

There’d be no pre-mine. No founder allocation. No speculative tokenomics sleight of hand. Just pure access—anyone could participate, and everyone would start equal.

This “no-premine, no privilege” approach is inspired by early Yearn Finance’s launch—zero reserved supply, no insider deals, just smart contract and community.

There are also no splits or skim fees on deposits; unlike some protocols that reserve, say, 10% of each mint for the team or treasury, $TIPS mints 100% to the depositor.

Rewarding Loyalty: Redemption Curve Encourages Long-Term Holding

Cash-out mechanics are locked from day one. That means the only way out is via the bonding curve, where the treasury determines your redemption value. That curve rewards loyalty and timing. Sell early, get less. Wait it out, the slope improves.

Early redeemers might only get 80% of their backing. That leftover stays in the pot, growing the share for those who stick around. It’s a protocol-native loyalty reward.

Borrow Without Selling: Unlock Value via REVLoans

And here’s the twist: you could tap into your $TIPS value without selling. Using REVLoans, holders can borrow against their position—accessing USDC while still holding their stake. It’s like having your inflation-fighting cake and eating it too.

This helps support long-term holders who believe in the value proposition but need liquidity in the short term.

Offsetting Inflation with Real Data

Let’s get practical. If inflation is 5%, a regular $1 stablecoin loses 5% purchasing power. $TIPS, by contrast, aims to grow in value (in USDC terms) by roughly that same 5%, offsetting that loss.

This may be achieved through a combination of controlled issuance and redemption penalties. As the quarters roll on and issuance slows, the average USDC per $TIPS rises—especially if demand increases due to rising USD inflation.

We’ll need to surface real inflation stats—like CPI from the Bureau of Labor Statistics—to contextualize progress. Not to peg, but to orient. There’s no automatic CPI peg here, just transparent references for anyone watching.

Conclusion: Big Picture of $TIPS

This wouldn’t be another farm-and-dump token. It’d be an experiment in programmable scarcity and stable purchasing power. By marrying the reliability of USDC, the principles of TIPS, and the autonomy of Revnets, $TIPS aims to be a smarter on-chain store of value.

The design choices – quarterly tapering, fair launch, no pre-mine, loyalty rewards – all serve a common purpose: to build trust and align the system with long-term users, not short-term speculators or insiders.

If you’re thinking about long-term DeFi assets that do more than just chase APRs, $TIPS might be worth watching.

No promises. Just math, mechanics, and a shot at holding a smarter dollar.

Sources: Real-world inflation data from BLS; Juicebox/RevNet concepts from Jango and Juicebox docs; TIPS bond mechanics from Investopedia/Schwab; Yearn’s fair launch philosophy.

Find a typos? I leaned on AI but touched it up a bit and you know what that means... call it out in Farcaster or The Base App and I'll send you a noice or tipn tip.

O Captain! my Captain! our gameweek trip is done,
The match is played, the points are in, the leaderboard begun,
You braved the benching whispers, you wore the armband proud,
All eyes were on your boots today, you drew the hopeful crowd.

But O heart! heart! heart!
O shots that hit the post,
Where on the pitch my Captain lies,
Gone missing like a ghost.

O Captain! my Captain! rise up and take a bow!
Rise & hear the fans still chanting loud, the clean sheet’s safe for now.
For you, the cheers & memes explode, for you, the frame is cast,
For you the boosts were reallocated, your moment here at last.

Here Captain! dear father!
This call beneath the sun,
It matters not if goals were scored
You dared to choose The One.

A team of AI agents
Flexible, reusable, shareable context
Dynamic feeds with persistent memory

Join the waitlist.

The team is starting small—inviting a few people into an early version as bugs are squashed and the infra firms up.

It’s been amazing to see this vision of @scottw’s come to life after years of work.

--
I’m an active advisor and a founding shareholder in the company. There is an open SAFE. hmu if you want an introduction.

Traditional equity incentives keeps builders waiting behind cliffs, vesting schedules, and exercise windows.

Front-Loaded Ownership Warrants (FLOW) flips this upside-down:

• Tokens sit visibly in escrow from day one.

• The issuer gets liquidity up front, minus prepaid interest, can be used to fund immediate operations.

• Holder controls timing: send a fixed repayment to unlock the tokens.

• Grace period built-in (thanks to prepaid interest), followed by a gradual collateral decay to zero wo cliff-edge expiry risk.

• Fully transferable NFT holder may sell, hodl, or swap anytime.

Certainly! Here's an example added to the end of the blog post:

Example of FLOW Mechanics in Action

Imagine a scenario where a project team holds tokens from their Revnet project and decides to put these tokens up as collateral for a loan. The loan is structured as a Front-Loaded Ownership Warrant (FLOW) represented by an NFT. This NFT is then given to a network contributor as an incentive.

Recipient Actions:

1. Immediate Access: Upon receiving the FLOW NFT, the recipient can see the exact token stack parked on-chain in escrow from day one.

2. Token Control: The recipient has control over the timing. They can send a fixed repayment amount in ETH to the contract to unlock the tokens.

3. Grace Period: A prepaid grace period is built-in (e.g., 2 years). During this time, the escrowed tokens will not decay only after that a linear decay kicks in until year 10, at which point the value hits zero.

4. Appreciation Strategy: If the ETH in Revnet appreciates significantly, the holder may choose to:

   • Early Exercise: Pay off the loan early to retrieve all tokens.
   • Reallocation: Reallocate the loan to access the appreciated value, adjusting the unlock price to reflect the current market conditions.

In this way, FLOW mechanics allow for flexible ownership and incentivize contributors to participate actively in the network's growth and success.

In short: Ownership flows the moment you pull the trigger, not when HR paperwork says it does.

At the Footy App, we're going to try this and see what we learn and see if find a better way to keep incentives aligned.

Squeeze to find out if the juice will FLOW. https://farcaster.xyz/miniapps/vRlFDfogkgrw/footy-app

Money define economies. Tokens define modern economies. Some thrive on speculation, while others build stable financial networks or reward long-term contributors. Whether it’s a memecoin designed for viral growth, a security token tied to dividends, or a network token governing an ecosystem, every token economy requires a system that can sustain itself. The problem isn’t just issuing tokens—it’s ensuring that they circulate in a way that rewards actual participation and maintains value over time.

Revnet.eth.sucks introduces a structured approach where tokens are always issued to those paying into the network. Instead of arbitrary supply or inflation, participants receive tokens as a direct function of their contributions. They can either cash out immediately for an instant rebate or hold onto their tokens, benefiting from future contributors, shifting incentives, and preset economic stages. Unlike traditional tokenomics, where governance votes or centralized control can change fundamental rules, Revnet enforces economic permanence—issuance rates, cash out tax rates, and operator splits are locked at deployment. The only thing that remains flexible is how operators use their split, allowing for strategic adaptation without undermining the foundational rules of the system.

A Token Taxonomy That Drives Economic Design
A16Z’s token taxonomy framework visually maps the different ways tokens derive value. Some, like memecoins, rely entirely on social speculation, while others, like security tokens, function as investments tied to real financial returns. In between, there are network tokens, arcade tokens, company-backed tokens, collectible tokens, and asset-backed tokens, each with unique economic dynamics.

post image
Revnet.eth.sucks is flexible enough to support all of these models by structuring token issuance, cash out costs, and revenue distribution in a way that aligns with the desired outcome. The table below outlines how different tokens function within this system.

Token Type Comparisons and Revnet Configurations

Revnet ensures that tokens are only issued to participants who pay into the system, preventing unchecked inflation and creating a self-balancing token economy where each participant must decide whether to cash out immediately or hold for future value.

Locked Rules, Adaptive Incentives
Revnet guarantees that a token’s issuance rate, cash out rate, and operator splits are set in stone at launch. This immutability ensures long-term predictability for participants, eliminating governance risks or sudden economic shifts. However, while the percentage of operator splits is locked, the operator retains full control over how their allocated funds are used.

For example, a network token’s treasury might initially fund growth incentives but later redirect funds toward security upgrades. A company-backed token could start with R&D funding, then later prioritize user rewards or token buybacks. A security token might shift its dividend payments from cash to reinvestment, adapting to changing market conditions while staying within the fixed economic structure.

This separation of locked rules and flexible allocations allows for dynamic strategy shifts without disrupting the integrity of the token economy.

The Participant’s Choice: Cash Out or Hold for Future Benefits
Since tokens are only issued to those contributing to the network, each participant faces a decision: take an instant rebate by cashing out or hold for long-term value.

Cashing out immediately means selling tokens for a rebate, reducing the cost of participation. Holding onto tokens, however, provides exposure to future network growth, additional contributors paying into the system, and potential inflationary or tax rule adjustments that were preset at deployment. This self-balancing dynamic ensures that both short-term liquidity seekers and long-term holders find a role within the system.

Pre-Programmed Economic Stages for Long-Term Viability
Even though Revnet’s core parameters cannot change, economic phases can be preset at launch to create structured incentives at different stages. A network token, for example, may begin with high issuance and low cash out tax to encourage early adoption. As the ecosystem matures, issuance might slow down while cash out taxes increase, reinforcing long-term holding and discouraging speculative exits. In later phases, issuance could cease entirely, shifting the focus toward governance and treasury sustainability.

These stages are predefined before launch and cannot be altered, ensuring predictability while still allowing for dynamic economic incentives over time.

Deploying a Token Economy on Revnet
Launching a Revnet-powered token involves committing to a fixed economic structure with three key settings:

• Issuance Rate: Defines how tokens are created and distributed.

• Cash out Rate: Determines the cost of leaving the ecosystem.

• Operator Splits: Allocates revenue to different stakeholders.

Once deployed, these settings are immutable. The only flexibility comes from how operator-controlled funds are spent, allowing for adaptive economic planning while maintaining foundational stability.

Why Revnet Creates Sustainable Token Models
Traditional token models often suffer from either unchecked inflation, unpredictable governance changes, or incentives that become misaligned over time. Revnet solves these issues by ensuring that tokens are only issued to paying participants, economic rules are locked from the start, and operator splits can be dynamically managed without altering the core framework.

For memecoins, this means hype can drive adoption without risking excessive supply inflation. For network tokens, it ensures that long-term infrastructure incentives remain stable. For security tokens, it guarantees investor confidence by preventing economic manipulations. By maintaining a clear, predefined structure with flexible execution, Revnet enables token economies that can sustain themselves across different market conditions.

Revnet.eth.sucks offers a reliable foundation for token economies, ensuring that issuance, taxation, and revenue allocation remain fixed while allowing operators to adapt their spending strategies over time. By structuring token issuance exclusively around those who contribute to the system, Revnet aligns incentives between current and future participants, creating a model where liquidity, governance, and sustainability work together seamlessly.

Whether launching a viral memecoin, an investment-grade security token, or a governance-driven network asset, Revnet ensures that every token economy remains stable, predictable, and strategically adaptable over time.

PS: Revnet mastermind @jango.eth modified the a16z image, stating, "Feels simpler."

Originally posted on Paragraph April 5, 2025

We’ve come a long way from typing cryptic commands on black-and-green monitors to effortlessly swiping, tapping, and speaking directly to our devices. Each evolution of technology has introduced new ways to interact—new verbs like “click,” “drag,” “scroll,” and “tap” that feel second nature today. But as AI matures, how might our language of interaction evolve next?

Historically, shifts in technology have expanded how we interact with our digital tools. The command-line era taught us verbs like “execute,” “compile,” and “run.” With graphical user interfaces, we learned “point,” “click,” “drag,” and “drop.” The internet and mobile revolutions gave us “swipe,” “pinch,” “zoom,” and “scroll.” These weren’t just new actions—they were new paradigms, reshaping how we think about engaging with technology.

Now, as AI becomes more integrated into daily life, we stand at another fascinating crossroads. AI interactions are less about direct manipulation and more about intention, guidance, and creativity. We’re already familiar with verbs like “prompt” or “generate,” but what other interactions might AI enable?

Imagine a future where interactions include verbs such as “imagine”—instructing your AI to visualize an entirely new scenario, “collaborate”—partnering directly with AI to co-create content, or “personalize”—asking your AI agent to adapt its responses uniquely to you. Instead of simple execution, interactions might shift toward actions like “infer,” where AI helps us understand complex patterns, or “augment,” allowing the AI to enhance our ideas seamlessly and intelligently.

This shift could fundamentally alter our relationship with technology. Rather than just issuing commands or navigating through menus, we’ll increasingly engage in meaningful dialogues—asking the AI to “clarify” its reasoning, “synthesize” complex information, or even “validate” the credibility of the content we encounter online.

Such changes won’t just transform our vocabulary; they’ll reshape our expectations and experiences. Our interactions might become less about control and more about collaboration—less about precise commands and more about thoughtful, intentional guidance, & hopefully winning together.

Of course, predicting the future of human-AI interactions is speculative. But imagining these possibilities highlights how profound the next shift in HCI might be. New verbs bring new paradigms (or did I flip that?), and the era of AI interaction promises verbs that not only describe our actions but reflect deeper, richer relationships with the technology itself & those using it.

What new verbs can you imagine using with AI in your daily life?

Hey everyone! After a much-needed break in wine country, I’m back in the dev trenches, and I’ve got some exciting updates. If you’re familiar with Score Square, the first money game on Footy App, you’ll be glad to hear it’s about to get a major upgrade. Inspired by the classic Super Bowl Squares and iirc an idea from @plantsnft for an MLB version, this update brings more flexibility to the contract, making it more customizable for future games accross sports and other use cases.

What's Score Square?

If you're not familiar with it, Score Square is a fun and easy game where players purchase squares in a grid that corresponds to a game score (e.g., in a football match). At the end of the game, winners are determined based on the final score. If you hold a ticket with that score line you win the pot.

Let’s dive into the major improvements made in the contract!

What's New in the Contract?

The contract much more flexible and customizable now, making it easier for anyone to deploy and run their own Score Square games or great their own app. Here’s what’s been added:

1. Customizable Asymetric Grid Sizes:
   The contract now supports arbitrary row and column sizes up to a maximum of 255 rows and columns. This flexibility means you can scale the game to any number of possible outsomes. 0 - 9 for American football or NBA games where the last digit of the score determines the winning square. Get creative and use it for wine and cheese pairing contest.

2. Payment Flexibility:
   Games can now use any ERC20 token (the standard token on Ethereum) for payments. For Footy App, we’ll be using $SCORES Footy App Points, but anyone can deploy the game with their own token. The game creator (deployer) can select which token to use for the game.

3. Dynamic Community Fee:
   The community fee structure has been updated. Instead of a fixed 4% fee claimed from the game pot, the contract now issues the first ticket in every new game as a way to help fund the project and promote it. The deployer can also set their own fee percentage, providing flexibility in how the fee is handled.

4. Incentivizing Deployed Games:
   The deployer (the one creating and running the game) is responsible for promoting and refereeing the game. In return, they earn the fees from the game. This gives more people an opportunity to become entrepreneurs, running their own games and making a profit.

How Does This Work?

The contract is written in Solidity, and here’s a quick rundown of how it works:

• Game Creation: The deployer creates a game by setting the grid size, number of winners, token for payments, and referee. The first ticket in every game is automatically assigned to a fixed beneficiary to help fund the project.

• Ticket Purchases: Players buy tickets (squares), and the contract tracks ticket ownership. Once all tickets are sold, the game is ready for the finalization step. But before we can finalize, there’s an important step: randomizing the board.

  Once the game is sold out, meaning all the squares have been purchased, the contract randomly shuffles the squares to assign them to players. The game moves to the finalization stage, where the winning rows and columns are selected, and the prize pool is distributed accordingly.

• Winner Determination: The deployer may assign a referee that can finalize the game by selecting the winning rows and columns, along with the payout percentages. Players who own the winning squares receive a portion of the prize pool.

• Prize Distribution: Anybody may trigger the contract to distribute the prize pool to the winners based on the pre-set percentages and places determined at deploy time. This process also distributes fees to the deployer.

The contract code for Score Square games handles the entire process—from creation and refund processing to winner determination and prize distribution. The contract is flexible enough to handle various game setups and makes sure the right people get paid.

What’s Next?

I’ll be deploying these updates in the next few weeks, so Score Square will be ready for the upcoming soccer season. This version will give everyone the chance to run their own game, set their fees, and earn a portion of the prize pool. It's a simple but powerful way to engage with your community, run games, and potentially make some money along the way!

Is This Making Sense?

I know this is a lot to take in, but I’m excited about the changes and what this will mean for the Footy App community. The goal is to provide a more flexible and accessible game, one that gives deployers more control and rewards those who help promote and run them.

Let me know your thoughts or if you have any questions. I’ll keep you updated on the progress as we get closer to launch.

Hello, Revnet.

Revnet isn’t for everything. It’s not a replacement for equity or voting contracts. It’s a fit when the thing you’re building makes money (or plans to), and you want your early backers to be rewarded based on that money moreso than speculation.

Let’s get into it.

You're a fit for Revnet if...

You’ve got revenue, or it’s coming soon.
Maybe you’re charging subscriptions. Maybe you’ve got a weekly drop that sells out. Maybe your fans keep tipping you $DEGEN on Farcaster. If there’s money flowing in, a Revnet can wrap that flow, issue a token backed by it, and let people borrow against it or buy into future revenue.

You want to keep control.
You don’t want to sell equity. You don’t want to hand over governance tokens to randos. You’re just trying to ship and pay a couple bills. Revnet lets you raise money like it’s a loan, but backed by future income—not personal risk or debt collectors.

You’ve got supporters, not speculators.
Your community shows up for the long haul. They want you to win. They’d love a way to prove it and maybe even get rewarded if you pull it off. Revnet’s tokens are more like receipts for backing or claims on real progress, not tickets to flip if the concert sells out.

You’re allergic to tokenomics but still need to fundraise.
You don’t want to fake a DAO. You don’t want to write a 40-page whitepaper with made-up numbers. You just want a fair way to raise some money and show people how it’ll come back to them. Revnet's what you reach for when you're building in public, but without the airdrop math cosplay.

Maybe skip it if...

You’re not planning to make money. That’s okay. Some of the best things on the internet are free. But Revnet’s power comes from channeling revenue—if there’s nothing to channel, it’s the wrong tool.

You’re looking for a meme coin launchpad. Revnet doesn’t do hype. It’s boring, in the best way. It’s receipts, cash flow, and accountability. If you want line-go-up without work, look elsewhere.

You’re trying to sell governance. Revnet isn’t about handing over control. It’s about giving supporters a stake in success, not a vote on every button color. Use juicbox.money for that.

In closing

Revnet are for the indie internet. The small team. The not-quite-a-startup. The open source. public goods with a plan. The app that just needs a little juice. It’s for builders who’d rather ship than shill, and for backers who want to support without playing hot potato.

If that’s you, welcome. Let’s make the internet weird and sustainable again.

Michael has been a builder. Built tools, used tools, paid for tools.

Every month, his credit card statement told the same story: storage fees, AI services, group compute subscriptions. He wasn’t just using software — he was feeding it. Paying without pause. Supporting companies he believed in.

But there was always that dull ache:
“I helped this thing grow — and all I get is a receipt.”

No stake. No upside. Just rent.
Cancel the subscription and everything disappears. Stick around, and you’re just paying more to stay in place.

He realized something:
The more loyal he was, the worse the deal got.

The Discontent

It wasn’t just Michael. It was the entire model. Traditional SaaS treats every customer the same:

Pay upfront
Get access
Own nothing

You’re not a partner. You’re a line item.
Even worse: the company you support is raising from investors, not from you. The upside is reserved for the insiders. You are the revenue, not the stakeholder.

So when the product wins, you get nothing.
When it fails, you helped fund the loss.
And when it thrives — maybe even sells — your loyalty isn’t even a footnote.

Michael started calling it the Broken Loop.

The Flip

He sketched an idea:

What if software wasn’t leased like a hotel room… What if the prodcut was backed like a startup?

Instead of paying with a credit card, you deposit into a fund. You get access, sure — but also a project token. Something that proves you believed early. Something that connects your loyalty to the product’s journey.

If you stop using it? You get your unused funds back. If the app grows? That token might have utility or upside. If you love it? You top up your support — and stake your belief.

This wasn’t a subscription.
It was a relationship.

The Build

They are called Revnets — revenue networks.

They’re smart contracts that:

Accept deposits (USDC, ETH etc)
Issue project tokens in return
Charge a time-based fee
Let users reclaim their remaining collateral anytime

It’s a subscription. But onchain. And with skin in the game.

Each Revnet acts like:

Access stream – Pay as you go, service flows over time
Collateral vault – Take back what you don’t use
Loyalty layer – Tokens signal belief & grant perks
Trustless pipeline – Revenue flows directly, no middlemen

And the best part? Each product or feature can have its own Revnet. No gatekeepers. Just value flowing directly between the builder and the user.

The Test

Michael deployed one quietly. No paywall. No checkout flow. Just a Revnet that he was instantly a token holder in.

It felt fair.
It felt earned.
It felt like the first time subscribing didn’t mean surrendering.

Builders got capital without middlemen.
Users got flexibility without lock-in.
And tokens became more than access — they became proof of belief that could be stacked or snapped to other projects.

The Return

Now Michael’s focus is simple:
Bring this model to anyone building with users in mind.

Not just decentralized products — any product that wants to reward the people who show up early, support often, and believe deeply.

With Revnets, subscriptions don’t have to be dead money. They can be shared upside. Aligned incentives. Continuous access and trust.

Your subscription shouldn’t punish your loyalty. It should reward it.

Stop charging rent.
Start building relationships.

DRAFT 1 (struggling with the story line... putting it down... may not pick up again)

CREATE
TOGETHER

Transform Outcomes, Generate Equity
Tokenize Holdings, Engage Rewards

image shared by @jango

Even though my role in Revnet.eth.sucks and related Juicebox 'stuff' is relatively small, I’ll save this message and pull it out when times are tough.

🙏💜✌️

In any sustainable ecosystem, the initial momentum is critical. For original content creation platforms, funding creators to produce high-quality original content is essential for several reasons:

1. Creating Initial Value
   The flywheel starts with original content creation—without it, there's nothing to engage users, and the ecosystem cannot begin to grow. Funding creators ensures that high-quality, engaging original content is consistently produced from the outset, attracting both consumers and supporters.

2. Reducing Barriers for Creators
   Many creators, especially in the early stages, face significant financial constraints. They may lack the resources to produce original content at scale or invest in the tools and equipment needed to create high-quality work. By funding creators, platforms reduce these barriers, ensuring that creators can focus on producing valuable original content rather than worrying about upfront costs.

3. Driving Early Adoption
   To kickstart user engagement, networks need something to bring users in and original content is the most effective driver. Funding creators to produce original content directly leads to the production of the type of content that attracts early supporters. This helps build initial traction for the creator's network and signals to supporters that there's a commitment to fostering an engaging environment.

4. Attracting Quality Creators
   Creators are more likely to engage with a network that provides financial juice and incentives. If creators know they can rely on funding from their work, they’re more likely to commit time and effort to produce high-quality original content. This is especially important in competitive environments, where creators have many choices for where to post and share their work.

5. Ensuring Sustainability
   Without a clear incentive to create original content, networks risk an initial surge of content but a slow decline as creators become disillusioned with monetization opportunities. By funding original content creation, and helping establish a sustainable cycle of high-quality original content production that drives ongoing engagement, fan investment, and growth.

6. Fueling the Flywheel
   Once creators are sparked, they can generate revenue through fans, who, in turn, receive tokens and incentives. These supporters become promoters, expanding the reach of the content and attracting even more creators. The initial funding acts as the spark that sets the flywheel in motion, where each phase strengthens the next and original content creation leads to more revenue, which leads to more promotion, which attracts more creators, and so on.

By investing in 'original' content creation upfront, networks set the stage for long-term success, driving both creator engagement and user growth. This initial funding acts as the necessary catalyst for the ecosystem, ensuring that the flywheel is effectively set in motion and gains momentum over time. Farcaster is getting this right. A few more revs and reward calculations tweaks and up we go...

If you've spent any time online, you’ve experienced the flood of ads that disrupt your browsing experience. They're everywhere—pop-ups, banner ads, interstitials, and sponsored content that invade your feed and demand attention. Some even play videos automatically or take over your screen entirely. It's the same story across websites and apps: you're going about your day, only to be interrupted by a loud, intrusive ad that forces you to pause everything you're doing.

The problem is deeper than just being annoyed—these ads aren’t just pushing products or services; they often blur the line between what's authentic and what's paid for. Interstitial ads, in particular, ride that line dangerously. These ads often look like part of the content, but they’re actually paid placements. They appear to be organic, yet they’re paid for, and the opacity of this dynamic leaves users feeling manipulated. This lack of transparency makes it harder for users to trust the content they see, as they can't always distinguish between genuine information and promotional material.

As John Wanamaker, a pioneer in marketing, famously said: "Half the money I spend on advertising is wasted; the trouble is I don't know which half." This sentiment still rings true today, as billions are spent annually on ads, but their effectiveness remains uncertain. In Web2, ad systems have created a disconnect between advertisers and consumers. Ads are pushed into users' faces, often with little regard for the users’ actual needs or interests. Worse yet, these ads usually track your every move, collecting data for hyper-targeting, which many users find invasive and unsettling.

The whole advertising ecosystem is broken. It’s clear: something needs to change. We deserve a system that feels more authentic and respectful of user privacy one that is transparent and effective without being manipulative. This is where amplified promotions in Web3 can step in and potentially reshape the entire landscape.

A New Direction: The Emergence of Amplified Promotions

Amplified promotions offer a new approach that addresses the flaws in traditional ads, focusing on transparency and meaningful engagement. Unlike the murky divide between organic and paid content on most platforms, amplified promotions provide clarity on what actions users are rewarded for and why. This is driven by attestations verified actions that are publicly recorded, traceable, and tamper-proof.

These attestations not only capture onchain actions but also include offchain attestations, offering a fuller view of user engagement. Rather than simply mimicking your social graph, these platforms ensure actions are verified both online and offline, meaning users' preferences, actions, and choices are validated with integrity. This shifts the focus from shallow engagements, like likes or shares, to real, impactful actions, making the entire promotional model more transparent and accountable.

A new system should put users at the center and in control they can choose when to interact with promotions, reveal their preferences, and toggle ads on or off as they wish. Unlike traditional models where ad brokers dictate engagement, users now have agency over their digital experiences, ensuring promotions feel relevant and respectful to their choices.

Navigating the Road Ahead

In this new system, there are delegated signers—which means that users can choose to grant permission to advertisers to send promotions in their name. In simpler terms: Yes, advertiser, I like your offer and your money, and I'm willing to act as an amplifier for your promotion. By using delegated signers, users maintain control over their engagement while still allowing advertisers to reach them in a respectful and user-approved manner.

However, this approach requires finer, more granular controls that are entirely user-centric. Users should be able to set specific preferences on how and when they interact with promotions. From deciding what types of ads they want to amplify, to selecting which advertisers they’re willing to engage with, these controls will enable users to have a customized and transparent experience. The key is putting the decision-making power in the hands of the users, allowing them to have full control over their interactions with advertisements.

This model challenges the traditional one-size-fits-all advertising system, where advertisers dictate the terms of engagement. Instead, users will be empowered to manage their own digital experiences, ensuring that promotions feel relevant, respectful, and aligned with their preferences.

The Future: A New Era of User Engagement

So, what does the future hold for amplified promotions? We’re only scratching the surface, but it’s clear that this new model will enable more meaningful user engagement. Platforms & apps that embrace this model will need to strike a balance: they must respect users’ time, privacy, & attention, while also driving real actions that lead to conversions.

For creators, brands, & decentralized projects, this presents a unique opportunity. No longer are you limited by traditional advertising metrics. With amplified promotions, you can engage users in ways that feel more personal, more rewarding, & ultimately more valuable. The key to success will be making promotions that users want to engage with, rather than pushing irrelevant content into their faces.

As Web3 continues to evolve, the rise of amplified promotions will likely signal the death of traditional, interruptive advertising. A new era of user-driven, blockchain-powered promotions is coming and it’s going to be an exciting ride.

The Wild Ride Ahead

We’re at the beginning of something big. Amplified promotions have the potential to transform how we think about user engagement, attribution, & privacy in digital marketing. While there will be growing pains, the opportunity to build a more effective, user-friendly system is within reach.

The real question is: who will seize the moment & lead the way? The platforms that can strike the right balance between rewarding users & respecting their privacy will be the ones that thrive. So, as the industry evolves, one thing is certain the journey ahead will be anything but boring. Stay tuned.

I rolled into Bannyverse,
I was feelin' about half past spent;
I just need some tokens to get my project rent.
"Hey, Banny, can you tell me where a man might get some aid?"
He just grinned and shook my hand, and "Juicebox," was all he said.

Take a loan off Banny, loan off Banny,
With tokens flowing free, you’ll see it through.
Take a loan off Banny, loan off Banny,
Come on now, join the crew!

I picked up my token, went lookin' for a place to hide,
When I saw Banny and the Juicebox walkin' side by side.
I said, "Hey, Banny, come on, let’s get this rolling now."
He said, “I’ve got you covered, let me show you how.”

Take a loan off Banny, loan off Banny,
With tokens flowing free, you’ll see it through.
Take a loan off Banny, Bannyyyy,
Come on now, join the crew!

Go down to the network, there's nothin' you can say,
It’s just ol’ Banny, and Banny’s here to pave the way.
"Well, Banny, my friend, what about that loan today?"
He said, "Just take it easy, the tokens come to play."

Take a loan off Banny, loan off Banny,
With tokens flowing free, you’ll see it through.
Take a loan off Banny, Bannyyyy,
Come on now, join the crew!

Crazy Banny followed me, and he caught me in the fog,
He said, "I’ll fund your project, if you'll just take Jack, my dog."
I said, "Wait a minute, Banny, you know I'm a peaceful man."
He said, "That's okay, boy, just let the tokens flow as planned."

Take a loan off Banny, loan off Banny,
With tokens flowing free, you’ll see it through.
Take a loan off Banny, Bannyyyy,
Come on now, join the crew!

Catch a token now, take it down the line,
My project’s sinkin’ low, but I do believe it’s time.
To get back to Banny, you know he's the only one,
Who sent me here with his token for everyone.

Take a loan off Banny, loan off Banny,
With tokens flowing free, you’ll see it through.
Take a loan off Banny, Bannyyyy,
Come on now, join the crew!

Two prompt song. wdyt?

What if supporting a project didn’t end with a transaction, but opened a relationship—liquid, ongoing, and mutual?

That’s what the Revnet Network is quietly making real.

In this model, a supporter contributes ETH, USDC, or any accepted token to a project they believe in. But rather than receive a thank-you or speculative reward, they’re issued project tokens—claims on the future revenue of the project itself. These aren’t passive badges. They’re programmable assets, backed by what the project actually earns over time.

And when supporters want access to value today, they’re not forced to sell and sever their alignment. They can borrow.

Borrowing against project tokens allows supporters to stay connected while unlocking liquidity. The tokens act as a type of collateral, and ETH or USDC is issued immediately. When the loan is repaid, the tokens are returned. Some prepaid interest and a small fee flow into the Revnet Network and are converted into $REV for the borrower.

This is the engine. A cycle that reinforces itself. Support flows in, tokens go out, value comes back, and each fee strengthens the network that made the transaction possible. It’s a circular economy in the most literal sense—project to supporter to network to project again.

Compare this to what passes for innovation in the meme economy: tokens built on hype alone, value based on little more than timing, being in the know, and—if there’s utility at all—it vanishes the moment the price dips. There’s no lending there, no revenue, no composable structure. Just volatility under the shroud of community and insiders. In contrast, Revnet tokens are tied directly to project outcomes, supported by real payment flows, and integrated with contracts built for reuse, not replacement.

The most powerful dimension of this model, though, isn’t financial. It’s architectural. Dial up or down the levels of speculation and loyalty you want to incentivize participation.

Revnets are composable. The same primitives that govern token issuance, borrowing, and repayment can be adopted by any project. That makes the network extensible. Projects aren’t isolated—they’re linked. Each one becomes a new entry point into the loop, and every use reinforces the whole.

Which is why the convergence with Farcaster is so meaningful.

On Farcaster, a new wave of app builders is emerging. These aren’t massive platforms trying to own the experience. They’re independent developers creating expressive, modular “mini” apps—but it still feels more like passengers on a bus than entrepreneurs driving it. And yet, we’re starting to see signs of something more: automated tipping, innovative promotional tools with bulletproof attribution, value flows that actually make sense. A leaderboard here. An arcade over there. We’re getting there. But there’s still work to do.

These apps shouldn’t be competing for dominance. They build on and next to each other. They pass users and value between them. And with Revnets, they can do something rare: share infrastructure without giving up autonomy. Each app can issue its own token, manage its own flows, and connect directly to the broader economy. Supporters can interact, borrow, repay—all without leaving the network or ceding control.

This isn’t a “framed” garden. It’s a growing lattice. Each project, each app, each contract is a node. The network isn’t dictated by centralized ruler or monetized by extractive layers. It expands outward, governed by use, strengthened by shared—yet amorphous—alignment.

The internet was always meant to have money built in. Not as surveillance or ads, but as native, participatory flows. Now, finally, it does.

Revnets offers a hopeful return to what the internet could have been. And, more importantly, a launchpad for what’s next.

Its spirit recalls Project Xanadu, the original vision for an interconnected, versioned, permissionless web. That project never shipped. But in the composability of Revnet and the openness of Farcaster, we can see its ghost: not just documents linked forever, but value and support linked as well. Not platforms that hoard attention, but networks that reward participation.

The future doesn’t need to be rebuilt.
It needs to be reconnected.

And that connection—between people, projects, and the flows that fund them—is finally live.

Then, I sent Colleen something snarky and she laughed out loud, and that’s when it hit me — this is something special. The idea that I could talk to someone across the room or across the world in real time was magical.

Those little yet profound moments are what we need more of now. Think back to that feeling you get cresting the top of a Ferris wheel, that rush of excitement as the world opens up in front of you. It’s the same feeling when you first tried infinite scroll on your iPhone or when you finally figured out point & click, drag & drop.

We need to capture that same sense of discovery with Farcaster. That moment when everything clicks, and you know that something big just shifted. It’s not about the tech — it’s about the feeling that something amazing is about to happen. Let’s find that Farcaster "A-ha"!

My response to this cast by @dwr :
https://warpcast.com/dwr.eth/0x2ca3e78a

Official is such a whitelisted word sigh

I think it's important to remember:
Protocols are rules, not entities.

It feels like the framing around this has been off for a while, and I believe that continues to be the case today. It has lead to suboptimal decisions that impact the network.

Uniswap is cited as an example but that doesn’t quite resonate with me in the way it’s set up as a justification. It’s something that makes me reflect on centralization, value extraction, and a community that was baited and switched. I'd have zero issues with a Business Source License (BSL) for MerkleM's 'Farcaster' front-end which currently dominates. There's no doubt that's a hugely important piece of the stack. Let's not force the entire ecosystem into one team's design decisions and timeline at the App level of the stack. It's the easy part of the stack to change and creates ripples in the pond the rest of use try to develop in.

Diversification reduces risk and divergence is the key to evolution.

That said, I truly appreciate the work Dan and the team have done. They've kept the large majority of their promises, which is worth recognizing. However, I believe it's time to move away from the "app-led protocol" approach—it's become bloated and has abused devs.

I've shared more and somewhat related thoughts in posts on this site using the tag 'farcaster'.

draft - have to clean up some of the ai embelishments

Introduction

Imagine walking into a room where every conversation, document, image & action is recorded in your photographic memory. That is the essence of a context container. In the Web3 world where messages often feel scattered across feeds, context containers could offer a way to gather everything related to a topic, project or moment into one persistent workspace. For newcomers, think of them as a blend of a chat room, a shared whiteboard & a ledger—spaces that remember everything you do.

The Problem with Feeds

Traditional social feeds feel like sheets of paper sliding under a door. You glimpse a post, then it vanishes under new updates. There is no memory, no natural progression, and no easy way to pick up where you left off. Important conversations fragment. Workflows stall. It invites a question: what if there were a better way to weave interactions together?

Context Containers? Say what?!

A context container could offer that better way. Instead of scattering your conversations across apps and feeds, it gathers them into a unified workspace. Imagine planning a group trip: you share an itinerary, attach a hotel map, ask a friend to confirm the booking & send a deposit—all in the same living space. Every message remains beside the payment receipt, making the whole story traceable.

At a technical level, context containers would reference or wrap both data & state. Data could include text, files, polls, images or links if it's digital it can go in there. eg. virualized services from enterprise SaaS applications. State could describe the condition of these elements, like whether a poll is still open or a payment succeeded. What if you could return minutes, days, or months later—and the story remained intact, ready for you to continue?

Dynamic Updates & Persistence

Some context containers might be ephemeral, glowing like candles during an active session. Others could persist like time capsules buried in decentralized storage or anchored onchain.

What if updates flowed naturally inside a container? Comments, task completions or file uploads could appear instantly, without refreshing. What if your workspace stayed alive even after your device crashed or you logged off—ready to pick up exactly where you left?

Dynamic updates and durable persistence could make context containers an ideal foundation for long-term projects, communities and collaborations.

How Context Containers Transform Interaction

Today’s feeds feel like bulletin boards, messy and fleeting. Context containers feel more like curated libraries where each book leads to the next, or nature trails where every landmark tells part of a bigger story. You could scroll back through timelines, reopen old discussions, or branch off new ideas—all without losing your footing.

Imagine coauthoring a recipe: you list ingredients, suggest substitutions, attach photos & jot tasting notes. Everything stays visible. Visibility could become the key—every action & update laid out clearly, without requiring constant prompting or hunting.

What if we thought about interacting with Farcaster sessions this way? Without visibility, using context feels like the early days of computing—like navigating a DOS prompt, where you must know exactly what to ask every time. With context containers, discovery could flow naturally, more like a graphical interface where options appear visibly and choices unfold before you. Instead of guessing, users could move intuitively from one action to the next.

Why AI Agents Need Context Containers

AI thrives on memory. Without it, AI feels fragmented, starting from scratch each time. Inside a context container, an AI agent could remember your preferences, your unfinished tasks, your prior decisions. It could suggest the next move, summarize conversations, or automate reminders based on the living context.

What if instead of reacting blindly to single prompts, AI could become a true collaborator—building with you over time, understanding your full journey?

Elevating FIP-2 in Farcaster

Every action a user takes in Farcaster—whether posting a cast, reacting (such as liking), or linking (such as following)—is created by a signer. Typically, a user delegates signing to an app, which creates messages on their behalf. This structure lets users retain ownership while enabling smooth interactions.

In Farcaster, reactions express emotional responses like likes, while links form relationships like follows. If signer-linked information were indexed by hubs—now called Snapchain nodes—apps could more easily filter actions by context. A user’s full session, across many apps, could become visible and actionable, opening new layers of discovery and interaction.

FIP-2 plays a crucial role here. By standardizing a parentUrl field, it gives every message a way to connect to a broader context. What if every conversation, every comment, every action carried its context forward? Threads could form naturally across apps, wallets, and agents. Developers would no longer have to invent bespoke solutions to link conversations.

Each link in a context chain could be cryptographically verifiable—building an open, user-owned internet of sessions, not just streams of posts.

A Glimpse into Farcaster’s Future

Picture a world where every "mini" app you use carries your session and state under your control, and seamlessly shares it across other apps. You might ask an AI in a music mini app to suggest tracks based on your morning journal in a writing mini app. Later, a finance mini app might allocate tokens for an upcoming trip—all while staying aware of the larger context.

These mini apps could act as agentic companions: learning your habits, executing transactions onchain & respecting your permissions. Context containers would tie these experiences together, ensuring that your actions remain coherent, recoverable & meaningful.

If Farcaster embraces FIP-2 deeply, this future becomes possible. Threads form naturally. Context travels across environments. Agents can fetch full histories, draft reports, initiate payments or update shared documents—all powered by structured, verifiable sessions.

What if we built toward that future now?

Conclusion

Context containers could reshape online interaction by weaving together chat, documents, transactions & AI into seamless, persistent sessions. They could preserve the narrative of your work, your projects, and your communities—whether for hours or decades.

AI agents become true collaborators when rooted in rich, durable contexts. Farcaster could lead this evolution by making FIP-2 a cornerstone of its protocol—laying the groundwork for conversations that are complete, verifiable & lasting.

In a landscape dominated by fleeting posts, what if Farcaster chose to build the future where every session leaves a legacy?

Some guys are blessed with double entendres. JMac said it was incredible.

What if we did something like this:

• Frame Navigator API : allow seamless navigation between frames inside a session.
• Ephemeral frame session / state / storage: scoped to the session onHub or node, not onchain, fast & lightweight.
• Agent-readable context surface: structured session data agents can use to navigate, compose, negotiate on the user’s behalf.

Frames would stop being just a lowly embed & become Peers in the Farcaster network. App to App. Winning together.

They’d become composable markets where users & agents cooperate , transact, & build new experiences fluidly all onHub/node.

[turns off hot water first & hopes wet laptop continue to function]

As Farcaster grows, so does the need for clear, portable, and reliable ways for apps to declare their presence and capabilities. Recently, discussion has centered around using a .well-known/farcaster.json file hosted at a domain to serve as the standard manifest for apps.

While this approach may seem appealing at first glance, it carries significant drawbacks that deserve closer examination. By addressing these challenges, we can chart a more resilient, decentralized path forward.

The Problems with Relying on .well-known/farcaster.json

1. Operational Fragility

Hosting a .well-known/ path assumes you have fine-grained control over your server, CDN, or hosting environment. In practice, many modern app developers use managed services like Vercel, Squarespace, or Webflow, where modifying .well-known/ paths is difficult or impossible.

This adds friction at the worst possible point: right when a developer is trying to launch or update their app. If you need to file support tickets just to serve a simple JSON file, the system is creating barriers, not lowering them.

2. Web2 Hosting Assumptions

While DNS itself is decentralized enough for naming, serving a .well-known/ file reintroduces a Web2-style operational dependency. Developers must:

• Maintain hosting infrastructure.
• Serve the file over HTTPS.
• Keep control of both the domain and the server or CDN.

If hosting lapses, the manifest disappears, even if the domain is still owned. It's easy to own a domain. It's harder to guarantee uninterrupted access to a .well-known/ path indefinitely.

In this sense, .well-known/ locks developers into centralized hosting models, contrary to the long-term vision of a decentralized, user-sovereign network.

3. Incompatible (ish) with Decentralized Hosting

Emerging decentralized storage systems like IPFS and Arweave do not map cleanly to .well-known/ expectations. These systems address content by hash, not by path on a domain. Expecting a .well-known/ structure limits Farcaster apps to traditional Web2 hosting and creates a hard barrier to fully decentralized app deployments.

In short: we can't easily decentralize tomorrow if you bake in Web2 hosting assumptions today.

4. No Queryable Registry

Another major drawback is the absence of a queryable, verifiable registry. If manifests live only at .well-known/ paths, there is no global index or discovery layer that apps and users can easily tap into. Each domain must be queried individually, creating fragmentation.

Without a structured registry, it's harder to:

• Discover new apps.
• Verify the authenticity and freshness of manifests.
• Build ecosystem-wide services like app browsers, marketplaces, or analytics platforms.

Why are we here?

Let's not forget Web3 Values and that moving fast is going to break A LOT of things.

Before we look at the solution, it’s worth stepping back to remember what we are aiming for. These values might not be fully realized immediately, but they remain the north star:

Portability: Identity, data, and app metadata should move freely across platforms without lock-in.

User Ownership: Users, not companies, should own the keys, profiles, and records that define their online presence.

Decentralization: No single point of failure. Apps and identities should work across multiple hosts, storage providers, and protocols.

Permissionless Innovation: Developers should not need approval from a gatekeeper to deploy, update, or improve apps.

Composable Discovery: Data and services should be easily queryable, indexable, and remixable by anyone, not locked inside private silos.

Living up to these ideals won't be perfect from day one, but the architecture we choose should make moving toward them easier, not harder.

A Better Path: Verified Domains & App (Profile) URLs

Fortunately, Farcaster already has a tool that solves this more elegantly: App's have FIDs. Ther are verifications by FIDS. Why not Domain Verification?

Each app can already attach a profile.url field to its Farcaster profile/identity, cryptographically signed and verifiable. This opens up a much more flexible discovery system:

• Developers point their profile.url to wherever their app lives: a traditional server, IPFS gateway, Arweave URL, or anywhere else.
• The manifest can live at the root (/) or at a simple path like /manifest.json.
• No .well-known/ paths, no server-specific requirements.

This structure aligns perfectly with Web3 values:

Portability: Apps can move between hosts without losing verifiability.

User ownership: The app identity lives with the app dev's signer, not with their hosting vendor.

Decentralization: Developers are free to choose traditional or decentralized hosting without friction.

Queryable Discovery: Because manifests are tied to verified profiles, they can be easily indexed, searched, and aggregated across the ecosystem, enabling richer discovery and interaction.

Summary

Choosing .well-known/farcaster.json has introduced unnecessary friction, limit future decentralization, and tied Farcaster apps to Web2 hosting assumptions. It also fragmented discovery efforts by scattering manifests without a queryable index. Unless lock-in is Warpcasts goal this seems to be a very suboptimal design decision.

Instead, by leaning into the existing profile.url field and verification model, we can create a more resilient, future-proof system that empowers developers to build however — and wherever — they want, while strengthening the entire app discovery ecosystem.

As Farcaster continues to grow, it's essential to choose foundations that scale not just for today's hosting models, but for the decentralized internet of tomorrow.

Look at the giants:

Salesforce spends around 44 percent of revenue on sales and marketing.

Hubspot? 50 percent.

Snowflake? 60 percent.

Even Meta and Google, with enormous brand moats, spend around 10 percent.

The lesson: the biggest winners sell hard.

Now, zoom out. Think about all the money flowing through a project. Not just revenue from customers, but investments, tax refunds, affiliate payouts, grants, interest income, sponsorships. Every inflow is capital that can be put to work. Every outflow is an investment in growth, protection, or survival.

Business inflows:
Customer payments, investments, grants, tax refunds, rebates, royalties, affiliate income, resale proceeds, dividends, interest income, insurance payouts, loan draws, crowdfunding receipts, sponsorships, tips or donations.

Business outflows:
Salaries and contractor payments, inventory and supply purchases, ad spend and marketing campaigns, sales commissions and bonuses, engineering and R&D costs, customer acquisition expenses, debt repayments, rent and hosting fees, capital investments, cash reserves allocations, profit distributions, expansion costs, tax payments, customer refunds, insurance premiums, licensing fees, legal settlements.

The world runs on cash in motion. Yet most systems are built to observe that motion, not activate it.

Revnet flips the script.

Tokenize your project's cashflow: sales revenue, investments, tax refunds, grants, whatever moves. Turn every inflow and outflow into something staked, something transparent, something that invites ownership, participation, and upside.

Money in, money out. Grow it, show it, flow it. Tokenize it all.

More soon. It is just getting started.

It’s Sunday afternoon. My phone buzzes — a 312 number I don’t recognize.

The message is simple:
"Can you be in Tijuana Tuesday morning?"

I text back:
"Sure. Who’s this?"

Turns out, it’s a friend of a friend. He had a sales call scheduled in TJ but the Cubs had just clinched their first World Series berth in a hundred years. No way he was missing that game. So he needed someone to take his place. Fast.

Next thing I know, I’m booking a flight to San Diego.
Instructions are minimal:

Stay at this hotel.

Eat breakfast downstairs.

An Oracle sales rep will find you.

Tuesday morning, I’m at breakfast, nervously picking at some eggs. Like clockwork, the Oracle guy spots me, introduces himself, and we head out to his car.

We drive south until we hit a Jack-in-the-Box parking lot just north of the border. That's the rendezvous point.
Apparently, someone from the client is coming to get us.

So there we are: two guys in suits, standing awkwardly in the sun, surrounded by fast food wrappers.

Then a dusty pickup truck rolls in.
Driver’s wearing a cowboy hat.
He leans out the window and says:
"Get in. In the back."

No paperwork. No ID check.
Just hop in.

We climb into the bed of the truck, perching on the wheel wells like kids hitching a ride, and rumble our way across the border into Tijuana.

And that’s how it started.

This limitation among other things blocks adoption of FIP-2. Without the ability to set parentUrl, apps can’t create thread-aware replies, Frame responses, or comments that anchor back to a specific source unless they have a backend or want to run an expensive query to try to find a specific cast. As a result, structured conversations in alternative context-containers across the protocol suffers.

Adding parentUrl support to castCompose in the SDK would preserve user choice while enabling powerful new features like:

• App native replies
• Comments on IPFS or blog content
• Casts that stay connected to the context that sparked them ie less ephemeral

This appears to be a small change to the sdk that help apps guide thoughtful, contextual conversation without taking agency away from users & inserting signer/key exposure

What is @ampsfun

Farcaster users raise a hand to say, “yes, the accounts I follow may send a cast on my behalf for a price.” Each user sets that price. When a promoter who is followed by an opted-in user wants extra reach, they tap the original cast. Bingo—the cast is sent from the follower’s handle, visible to that follower’s audience, & the fee moves straight to the follower’s wallet. Attention gets routed, value flows, everyone sees what they earned.

What @ampsfun nailed

• Low click flow: anyone can push a recast into fresh feeds in seconds
• Friendly consumer vibe: zero wallet gymnastics, just pick a cast & pay
• Real market validation: creators already spend when distribution feels effortless

Gaps that invite the next wave

• Signer custody clarity: teams need to know exactly where signature delegation lives & why they stay safe and how to revoke them
~~
• Flexible spend limits: full USDC allowance spooks power users; lighter caps build trust~~
• Context based pricing: memes, deep dives & launches deserve separate knobs
• Programmatic spend: growth squads crave an interface they can script into daily campaigns
• Bulk recipient lists: let devs upload FIDs or addresses to seed niche groups quickly
• Event triggers: fire a recast automatically when context aligns, for example first cast of the day or a milestone post
• Scheduled boosts: timed drops multiply impact across regions & launch windows

Why it matters

Brands & apps will soon hold the biggest ad wallets on Farcaster. They need amplification that plugs into existing growth loops, not a single user pop up. Unless @ampsfun stretches toward that segment, someone else will fork the idea & capture the spend.

Path forward

1. Publish transparent signer delegation docs that anyone can audit and easily revoke
2. Offer simple entry points for creating, pricing & timing boosts
3. Add role based limits so interns cannot torch budgets
4. Return analytics hooks that pipe reach stats into everyday dashboards and apps

Ship these pieces & amplification becomes the default growth engine for Web3 native brands and eventually all brands. Expect fewer Web2 ads, more on chain fan journeys & a sturdy revenue pillar for the Farcaster ecosystem.

@ampsfun showed the way. The next move turns a spark into a bonfire.

Brainstorming with AI on how revnets can help with developmment & tuition

Direct financial wins for the school

-Immediate working capital
Families mint $TUITION months before classes start. The school books cash today instead of waiting for August tuition checks.

• Interest-free financing
  No bank line, no coupon payments. Tokens cost the school nothing to issue, so every pre-sale dollar is zero-cost liquidity.

• Predictable cash-flow calendar
  Clock-based stages lock in dates & prices. Finance can model deposits, bridge inflows & AMM redemptions with high confidence.

• Built-in scholarship fund
  Each mint & every cash-out streams a fixed % directly to the Scholarship wallet. The pot grows automatically, no annual appeal needed.

• Endowment snowball
  Automint slice feeds the Endowment wallet with tokens that track the 3 % annual price ladder. Rising token value compounds real asset growth.

• Stronger enrollment forecasting
  On-chain mints show who is financially committed long before acceptance letters. Admissions can right-size sections & staffing earlier.

• Lower tuition discounting
  Families prepay to lock lower prices. School captures full sticker revenue instead of offering traditional early-pay discounts.

• Inflation hedge
  Annual 3 % price step aligns with tuition increases, keeping real purchasing power intact for forward-year revenue.

• Buyback option improves margins
  If secondary trading dips below face value the treasury can repurchase tokens cheaply, retiring future liabilities at a discount.

• Transparent donor accounting
  Splits, wallet balances & burn events are on-chain. Auditors & families see exactly where every wei flows, slashing admin overhead.

• Broader donor funnel
  Crypto-native alumni & external supporters can contribute without complex wire instructions, expanding the capital base beyond current parents.

• Regulatory simplicity
  Immutable, rules-based Revnet keeps tokens in the “prepaid service” bucket, avoiding securities headaches & associated legal costs.

These levers together raise capital earlier, cut financing costs, grow scholarships automatically & give finance a crystal-clear revenue map.

A family’s journey with $TUITION

• Discovery & pledge
  In mid-February the Johnsons open the school’s Revnet page, connect a wallet, pick USDC, & click Mint $TUITION. One block later 10 000 $TUITION tokens—worth $10 000 of future tuition—sit in their address. Smart-contract splits fire automatically: 70 % flows to the operating treasury, 25 % to the Scholarship Fund, 5 % to the Endowment wallet.

• Receipt & CRM sync
  The UI pops a PDF tax receipt that drops straight into the family’s downloads folder. At the same time their wallet address & token balance push into the Admissions CRM, flagging them as a committed prospect.

• Quiet application season
  Fall arrives, applications open, & the Johnsons submit the usual forms. Admissions staff can see the on-chain pledge, so interviews & aid planning jump to the top of the queue. No tokens move during this phase; the family simply waits for a decision.

Enrollment contract & redemption
January brings good news: an offer letter. Inside the billing portal a Pay with $TUITION button is ready. One click calls approveAndRedeem, burns 10 000 tokens, emits a TuitionRedeemed event, & posts $10 000 against the ledger. Any leftover tokens remain in the wallet for future years or a sibling.

If admission falls through
Should the child land elsewhere, the Johnsons can cash-out during the in-semester window. The Revnet AMM swaps their tokens for USDC at the current price, less a 0.60 fee that respects the same 70 / 25 / 5 split. They can also gift tokens to another applicant or simply hold as a donation.

• Compliance & accounting
  Because each token redeems for a defined service—tuition—the position books as prepaid revenue, not a security. The burn event plus a USD oracle gives finance a clean journal entry:

• Experience at a glance
  Family POV: Mint early, lock the rate, stash the receipt, redeem next year with two clicks.
  School POV: Instant working capital, transparent scholarship funding, & a blockchain-verified queue of eager families.

I couldn’t agree more with Nat. https://warpcast.com/emodi/0xcf90f10c

[steps onto soapbox]

We’re building fast but on sand. The promise of crypto was never just about spinning up tools or launching yet another social network or web app to frame. It started long before Bitcoin, when a group of cypherpunks saw what the internet was becoming & decided to write code that could defend privacy, autonomy, & freedom—without needing permission.

Cryptocurrency was born from that mindset. That systems could be rebuilt. That data could be owned, not rented. That value could move freely without gatekeepers. That privacy wasn’t just a feature—it was the foundation.

‘Farcaster’ is drifting.

When devs are required to ask for API keys & approval to use Direct Cast APIs.
When notifications feel like closed loops only the host app controls.
When identity & verification/attestation get locked into a single app’s design choices.
When user preferences—like notifications, mutes, & labels—are created, stored, & enforced by individual apps instead of users.
And now, a growing wave of Farcaster “mini-apps” don’t even use crypto. Just centralized widgets riding on a decentralized graph of edutainment.

If all we build are features without values, we’re not moving forward.
The moment we trade principles for polish, we trade freedom for familiarity.
We can do better.

What can be done?
Don’t mix app-level thinking with protocol thinking. Keep them separate & open.

If there’s going to be app-level showcasing, highlight apps that couldn’t exist without the unique properties of crypto.

Move user preferences to the protocol so they are owned by users. Mutes, labels, notifications—these should belong to the user. The apps should log in to me.

Break the protocol into programmable primitives. Let many protocols compete for their place in the stack. DMs & attestations might be a good place to start.

Push back on “protocol-as-business” thinking that forgets protocol-as-commons. Fees & taxes should support the community.

Treat apps as peers, not subordinates.

Open Snapchain to support more than just social feed apps. It’s a graph—but why are there so few supported link types?

[steps off soapbox]

Get a notifications webhookUrl from pingem.xyz

<script type="module">
  import { sdk } from 'https://esm.sh/@farcaster/frame-sdk';

  async function inFrameContext() {
      const links = document.querySelectorAll("a[href^='http']");
      for (let link of links) {
          link.addEventListener("click", (event) => {
              event.preventDefault();
              sdk.actions.openUrl(link.getAttribute("href"));
          });
      }
      await sdk.actions.addFrame();
  }

  window.onload = async () => {
    try {
      await sdk.actions.ready();
      const ctx = await sdk.context;
      ctx ? await inFrameContext() : FrameBar();
    } catch (error) {
      console.error(error);
    }
  };
</script>
<meta name="fc:frame" content='{
  "version": "next",
  "imageUrl": "{{ social_image_url }}",
  "button": {
    "title": "See my innie",
    "action": {
      "type": "launch_frame",
      "name": "KMac has an innie app",
      "url": "https://kmacb.eth.sucks/{{ article.id }}/",
      "splashImageUrl": "https://kmacb.eth.sucks/avatar.png",
      "splashBackgroundColor": "#010513"
    }
  }
}' />

There one small gotcha as of today. The app manifest needs to be in a hidden folder on your domain called .well-known/farcaster.json That's doable but not yet automatic. Reach out if you are heading this way and I'll write something up. Other wise will want until that's build and the miting contracts are updated in the templates.

The AI Written Fable of the Shoreline Builders

Once upon a tide, in a coastal kingdom where software grew like coral and castles were coded from sand, there lived a community of builders. These builders were clever and curious, always looking to erect new structures—some floated on the breeze, others danced with the moonlight, but all depended on a stable shoreline to stand tall.

At the center of the coast stood the Grand Pier—a mighty boardwalk laid by a team of Appwrights. They invited everyone to build near it, promising stability, visibility, and the rhythm of constant foot traffic. “Why venture inland,” they said, “when all the waves of users crash here?”

The builders, drawn by the crowd, began to stack their dreams high beside the Pier. To hedge their bets, a few clever ones drove pilings deep—just in case the tide ever shifted.

Seasons passed. The Appwrights flourished. Their pier expanded with each sprint, tilting subtly toward their own storefronts, their own rules. The shoreline narrowed. Features changed overnight. One morning, a builder woke to find their door no longer faced the waves. Another found that their staircase now led nowhere.

The Appwrights shrugged. “We’re iterating,” they said. “It’s all for user experience.”

But the builders murmured. Their houses, once steady, had become brittle. Pilings cracked. Sand eroded. And though no storm had struck, the ecosystem buckled under the weight of one structure leading all others.

One old builder, whose hut was built furthest from the Pier and deepest on pilings, called out:
“We forgot the lesson of the sea: Piers rot, but the bedrock beneath still holds. Build on open ground. Align with the tides, not with the crowd.”

Some listened. Some moved. Some stayed.

And the shoreline remembered.

Moral:
When one app leads the protocol, all others are building on sand. Drive your pilings deep. Build for the tide, not the pier.

Croptop is kinda like instagram meets crypto or if you prefer wordpress meets crypto. I can’t help but think of Drupal back when it was just starting out with a community of devs extending it.

Anyway, there are a few big to dos to get Croptop to a place whene normal people can use it.

1 - The need for a hosted provider. Right now to publish one needs a downloaded app & that’s macos only
2 - Easie theme creation
3 - A template builder ui
4 - Farcaster & Telegram mini-app support
5 - Commenting system (farcaster FIP-2??)
6 - Get the EVM contracts in the ui

halfbaked idea
https://fc-footy.vercel.app/
add section for club supporters to share digital memoribilia that is mintable & builds a fan club treasury

Playing around with an idea for an onchain fantasy footy game of sorts

Content Authenticity finally moves into the public consciousness

drawn by @zeuzc

FC’s missed opportunity

Pondering how big the non-ownership properties are & why its not getting more attention.

Is ownership so easy to add that… why not have it on any data?

Riff'n on revnet pitch with the team

Just add water

You Never Listen

https://notebooklm.google.com/

Playing around with a lil something for ETH Denver. Find my Farcaster Friends.

Thinking this could be a so called Farcaster Frame Game

Playing around with data viz for defifa.

Playing around with the idea of AI assisted strategy games.

Thinking about adding this to d33m rooms as a presence indicator.

Playing around with framing defifa as a type of card game. Cards come in 5 colors, each color is a Team. Players may mint as many card as they wish granting them more relative voting power within a Team.

The simulator mocks the ‘mints’ ie draws on the infinte deck of playing cards.

The game could be played with the other players in a chat like interface with and AI assistant. eg. What aliances should player3 make?

To determine the best strategy for Player 3 to gain the majority vote in the game, we need to analyze the voting power they have in each team and identify potential alliances with other players.

Player 3's current voting power in each team is as follows:

• Red Team: 16.67%
• Orange Team: 40.00%
• Yellow Team: 33.33%
• Green Team: 25.00%
• Blue Team: 55.56%

For a team to vote for a pot split proposal, at least 50% of its voting power must agree. Therefore, Player 3 needs to form alliances with other players to gain the majority in at least three teams.

1. Blue Team: Player 3 already has a majority (55.56%) in the Blue Team, so no additional alliances are necessary here.

2. Orange Team: Player 3 has 40% of the voting power. Forming an alliance with any other player (each holding 20%) will secure a majority in the Orange Team.

3. Yellow Team: Player 3 holds 33.33% of the voting power. By forming an alliance with either Player 1 or Player 2 (each with 33.33%), Player 3 can secure a majority in the Yellow Team.

4. Red and Green Teams: Player 3 has less influence in these teams (16.67% and 25%, respectively). Forming an alliance in these teams might not be as beneficial unless Player 3 can form an alliance with Player 1, who holds a significant stake in both (50% in Red and 25% in Green).

Strategic Alliances for Player 3:

• Form an alliance with any player in the Orange Team.
• Form an alliance with either Player 1 or Player 2 in the Yellow Team.
• Optionally, consider an alliance with Player 1 for additional influence in the Red and Green Teams, although this is not strictly necessary to achieve a majority in three teams.

By following this strategy, Player 3 can effectively use their current card allocation to influence the majority vote in at least three teams (Blue, Orange, and Yellow), which is the requirement to control the pot split decision.

The chat interface enables coordination with other players whose interests may or may not align with Player3's as well as an assit from ai via /ai [ask question]. The ai has the context of the game as each phase.

https://site.api.espn.com/apis/site/v2/sports/soccer/eng.1/scoreboard

still rev’n on design & usability. Goal is to have a defifa.net game played within a chat interface.

In the meantime using it for chat during watch along football matches with farcaster frirends.

warpcast has a Twitter like intent. Format works like this

https://warpcast.com/~/compose?text=Hey+I%27m+in+this+pop-up+channel+smack+talk%27n+about+the+beautiful+game.%0A%0AClick+the+link+join+me%21%0A%0Ahttps%3A%2F%2Fd33m.com/lobby1

https://github.com/rev-net/whitepaper/blob/master/whitepaper/revnet.pdf

https://warpcast.com/kmacb.eth/0x3fb75579

Not digging this one.

We have no control over who becomes a member. Let’s not make value judgements here.

Professional operations are not needed. This smells like it’s paving the way for more ‘meta’ funding where members extract funds that should be used to proliferate... Zero ops is a better goal im

LFG

d33m.com

Careful out there people.

Revnets are not a replacement for corporations but rather a complement. They may serve as a rewards or loyalty point system for corporations, or they can function as independent treasuries without the need for a formal entity.

https://support.zora.co/en/articles/8192123-understanding-protocol-rewards-on-zora

Thinking about how a Channelin Farcaster could fund it’s mission and grow it’s membership.

revnet.app is coming along nicely

WC is his app. Not the BDFL that he is in Farcaster but this isn’t the way to rally devs.

Youngest got his license to drive today. Youngest had to call for roadside assistance today.

Inspired by fc/EatSleepCrypto’s writtings on tokenomics.

https://eatsleepcrypto.com/

Equation of Exchange Components

The equation of exchange, MV = PQ, describes how a token’s use as a medium of exchange drives its price.

Solving for M, the equation reads intuitively.

M = PQ/V

For any given time period, M, the monetary base is worth the total value of purchases (PQ) divided by the number of times each coin is used (V, velocity or churn).”

For example, if CashCoin is used to buy $1,000,000 worth of products per year, and each CSH is used an average of 5 times, the variables are as follows:

M, unknown (monetary base)
PQ = $1,000,000. (total value of purchases)
V = 5 (velocit
Solving for M using M = PQ/V gives us M = $200,000.

So the monetary base of CSH is $200,000.

Valuation Framework: Cryptocurrencies

Fundamentally, cryptocurrencies get their value through use as a medium of exchange. This includes…

https://www.eatsleepcrypto.com/articles/valuation-framework-cryptocurrencies

Equation of Exchange

The equation of exchange is a model that shows the relationship between money supply, price level, and other elements of the economy.

https://www.investopedia.com/terms/e/equation_of_exchange.asp

Price Floor

The equation of exchange can be applied at a high level to quickly calculate price floors of a currency based on a few inputs or assumptions.

In order to find components of a token's price floor according to the equation of exchange, (monetary base * velocity) MV = PQ (total value of purchases).

PQ - to find pull contract events and token transactions that take place within the token protocol.

V - find circulating supply and address balances over time. How many times was token used?

Price to Price Floor comparison in bear market

Circulating supply increase will drive down price but Base Monetary Value is the same.

Velocity

Figure out Circulating supply by looking at addresses. Omit locked tokens. % over a time period (need confirm this)

V = # Coins Sent divided by Circulating supply
Typically this is a number between 5 and 50 for blue chip ERC20 Token

#Leverage
See image above of a first-class mechanical lever

Tokenomic leverage mirrors mechanical leverage. Using the analogy of a first-class lever, we can say that:

Value being exchanged in a mechanism is the force placed on the long end of the lever.
Tokenomic leverage is the ratio of the distances of each force from the fulcrum.
And value captured is the output of force from on the shorter end.

But adding leverage to a token is one of the simplest, yet most effective ways to increase its price floor.

eg

• Staking requirements for an application decrease circulating supply proportional to that application’s use;

• Fee rate hikes for an application increase the demand for the token used to pay fees, proportional to that application’s use.

Token Flow

Tokens circulating in an ecosystem (circulating supply)
The value transferred between participants in an ecosystem (PQ)
The time a token takes to circulate, represented by length of all pipes (V)

Inflation Deflation

Inflationary assets continue to be created over time which drives
The time a token takes to circulate, represented by length of all pipes (V)

Follow fc/EatSleepCrypto

• aka Nate for deeper dive
• Profile on Farcaster https://warpcast.com/eatsleepcrypto/

WC is sponsoring the key registry for OG and active users to try additional apps in the FC eccosystme for free. They are sponsoring the key registration via an experiemental rewards program.

@filipv crushed it and created a handy Revnet simulator, Check out the impact of various deployment settings before launching.

Year 1 comes to a close for Purple DAO. The artwork will change. This could be the last purple square for quite a while.

No dumping on retail investors

@peace is riff’n on Revent logos. Digging the all caps with name spelled out.

Put this together a few years back for a presetation to Vodafone. Mathmatics has propelled commerce with a few big spurts…

Playing around with this framing for kicks. wdyt?

Testing some ideas out and checking out features of Croptop / Planet / Pinnable

Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.Developers.