mya retweeted
submitting The Pit for the @NEARProtocol #NEARHackathon.
It’s a memecoin launchpad on NEAR where each coin trades against its own reserve, earns an AI inference budget from fees and staking rewards, and lets holders shape what its AI remembers.
I wanted to give communities ther after launch. On The Pit, trading and staking fund the coin’s AI, and holders decide which memories become part of its voice.
Launch a coin in one transaction. Creators choose a name, ticker, image, an optional early-access window, and a creator share of up to 50% of harvested surplus. The factory gives each coin its own NEAR account with standard fungible-token transfers and metadata. NEAR Global Contracts let each coin reference the same hash-pinned code, bringing the base launch cost to about 0.12 NEAR before image storage. The testnet factory has zero access keys.
Trade against a staked reserve. Buys mint tokens along a bonding curve, and sells burn them. The reserve targets 80% staked and 20% liquid. When the liquid buffer can cover a sell, the contract initiates the payout immediately. Otherwise, it records a claim at the quoted sell price and settles it as liquidity becomes available. A permissionless keeper can rebalance the reserve, process queued payouts, and harvest surplus. The app also exposes tools for recovering refunds and confirmed failed payouts.
Set an optional early-access window. Buyers complete a challenge and a small proof of work to receive a short-lived, single-use pass. The contract checks that the pass belongs to the buyer’s wallet and the current launch window, and enforces the purchase cap. The testnet gate uses a development signing key and a mock agent registry. The mainnet plan includes a production NEAR Shade Agent running in a trusted execution environment.
Give each coin an AI budget with verifiable output. Staking rewards and a 1% trading fee contribute to the coin’s inference budget after any creator share. The brain service credits confirmed on-chain harvests to an off-chain ledger. As the reserve grows, the coin can advance through four tiers with different models and capabilities. Thoughts appear in the public activity feed, and the service supports optional Telegram posting and replies.
I integrated NEAR AI Cloud for Proof of Thought. When a signed thought is recorded, the coin contract verifies its Ed25519 signature. The browser can independently check the response hash and the NEAR AI attestation that binds the signing key to a trusted execution environment.
Let holders teach the coin. Holders can propose a memory and lock tokens behind it. Support grows with both the amount locked and the time it stays locked. Once a memory reaches the threshold and is adopted, it becomes part of the canon the AI reads when generating new thoughts. Holders can withdraw their tokens, and adopted memories stay in the canon.
Bring the tools into one app. You can browse markets, explore the bonding curve, trade, track holdings and creator earnings, look up payout claims, and inspect the coin’s thoughts and memories. I also built a RHEA funding flow that quotes routes from Ethereum, Base, and Arbitrum to native NEAR and tracks delivery to the buyer’s wallet. The app includes rNEAR market data and wallet-level staking, unstaking, and withdrawal controls. Those wallet positions are separate from coin reserves.
Where it stands. The Pit is deployed on NEAR testnet with a mock validator pool and agent registry. The repo includes an internal security review, local end-to-end rehearsals, and a 10,000-operation simulation covering reserve solvency, payout accounting, and token conservation. Before opening mainnet to public funds, I plan to get an independent audit, deploy with a real validator pool and the production Shade Agent gate, and verify payouts, harvests, and native NEAR delivery through RHEA with controlled transactions.
The part I’m most looking forward to is seeing two communities start from the same contract code and teach their coins to sound completely different. What would you teach yours?
Demo: trythepit.xyz
Code and docs: github.com/drained69/thep…
It’s a memecoin launchpad on NEAR where each coin trades against its own reserve, earns an AI inference budget from fees and staking rewards, and lets holders shape what its AI remembers.
I wanted to give communities ther after launch. On The Pit, trading and staking fund the coin’s AI, and holders decide which memories become part of its voice.
Launch a coin in one transaction. Creators choose a name, ticker, image, an optional early-access window, and a creator share of up to 50% of harvested surplus. The factory gives each coin its own NEAR account with standard fungible-token transfers and metadata. NEAR Global Contracts let each coin reference the same hash-pinned code, bringing the base launch cost to about 0.12 NEAR before image storage. The testnet factory has zero access keys.
Trade against a staked reserve. Buys mint tokens along a bonding curve, and sells burn them. The reserve targets 80% staked and 20% liquid. When the liquid buffer can cover a sell, the contract initiates the payout immediately. Otherwise, it records a claim at the quoted sell price and settles it as liquidity becomes available. A permissionless keeper can rebalance the reserve, process queued payouts, and harvest surplus. The app also exposes tools for recovering refunds and confirmed failed payouts.
Set an optional early-access window. Buyers complete a challenge and a small proof of work to receive a short-lived, single-use pass. The contract checks that the pass belongs to the buyer’s wallet and the current launch window, and enforces the purchase cap. The testnet gate uses a development signing key and a mock agent registry. The mainnet plan includes a production NEAR Shade Agent running in a trusted execution environment.
Give each coin an AI budget with verifiable output. Staking rewards and a 1% trading fee contribute to the coin’s inference budget after any creator share. The brain service credits confirmed on-chain harvests to an off-chain ledger. As the reserve grows, the coin can advance through four tiers with different models and capabilities. Thoughts appear in the public activity feed, and the service supports optional Telegram posting and replies.
I integrated NEAR AI Cloud for Proof of Thought. When a signed thought is recorded, the coin contract verifies its Ed25519 signature. The browser can independently check the response hash and the NEAR AI attestation that binds the signing key to a trusted execution environment.
Let holders teach the coin. Holders can propose a memory and lock tokens behind it. Support grows with both the amount locked and the time it stays locked. Once a memory reaches the threshold and is adopted, it becomes part of the canon the AI reads when generating new thoughts. Holders can withdraw their tokens, and adopted memories stay in the canon.
Bring the tools into one app. You can browse markets, explore the bonding curve, trade, track holdings and creator earnings, look up payout claims, and inspect the coin’s thoughts and memories. I also built a RHEA funding flow that quotes routes from Ethereum, Base, and Arbitrum to native NEAR and tracks delivery to the buyer’s wallet. The app includes rNEAR market data and wallet-level staking, unstaking, and withdrawal controls. Those wallet positions are separate from coin reserves.
Where it stands. The Pit is deployed on NEAR testnet with a mock validator pool and agent registry. The repo includes an internal security review, local end-to-end rehearsals, and a 10,000-operation simulation covering reserve solvency, payout accounting, and token conservation. Before opening mainnet to public funds, I plan to get an independent audit, deploy with a real validator pool and the production Shade Agent gate, and verify payouts, harvests, and native NEAR delivery through RHEA with controlled transactions.
The part I’m most looking forward to is seeing two communities start from the same contract code and teach their coins to sound completely different. What would you teach yours?
Demo: trythepit.xyz
Code and docs: github.com/drained69/thep…
4
7
9
398
mya retweeted
you've been finishing mid-table in FPL since 2019. well, it's time for a new league.
welcome to WIF League. NVDA as captain, TSLA up front, META in midfield.
fantasy football, but with stocks. no injuries, no rotation, no Pep ruining your weekend.
draft 5 Stock Tokens on our captain and enter with 1,000 $WIF.
Chainlink handles the scoring at the 21:00 UTC close. Top 3 split the pot, 10% gets burned.
small field, open podium. finally, a chance to win something.
built for @WIFonRH's World is Flat.
wifleague.nerom.site
welcome to WIF League. NVDA as captain, TSLA up front, META in midfield.
fantasy football, but with stocks. no injuries, no rotation, no Pep ruining your weekend.
draft 5 Stock Tokens on our captain and enter with 1,000 $WIF.
Chainlink handles the scoring at the 21:00 UTC close. Top 3 split the pot, 10% gets burned.
small field, open podium. finally, a chance to win something.
built for @WIFonRH's World is Flat.
wifleague.nerom.site
9
17
42
723
mya retweeted
we built strip: turn a boring changelog into a 4-panel comic, made with an ai agent.
paste the release note. pick one of three angles. edit a line, stamp it mine, and the agent can't touch it.
built on @builderio's agent-native. same action for buttons, in-app agent, and mcp.
r34LFT9
code: github.com/emmagh1/strip
paste the release note. pick one of three angles. edit a line, stamp it mine, and the agent can't touch it.
built on @builderio's agent-native. same action for buttons, in-app agent, and mcp.
r34LFT9
code: github.com/emmagh1/strip
Announcing the Agent-Native hackathon!
$10k in prizes. Come build agentic apps with us
builder.io/hackathon
10
13
35
1,413
mya retweeted
spendGuard is live on near testnet.
what does it do?
a coding agent that pays for API calls usually holds a key with money behind it. one poisoned readme, and it tries to spend past what you meant to give it.
SpendGuard moves the money into a contract. the agent keeps a l key that can call request_spend on one contract and nothing else. it can ask to spend. it cannot approve itself, change the policy, or touch the treasury.
when it asks, the contract checks four things at that moment:
- is the vendor on the allowlist?
- is the amount under the per-spend cap?
- does it fit the budget for this period?
- is it inside the rate limit?
you approve or refuse the from cli. every decision leaves a receipt either way:
- approved or denied.
- the rule that passed or failed.
- the amount, the vendor, what is left in the budget.
- a receipt id anyone can read from the public RPC.
the console shows the same receipts with no backend and prints the curl commands behind every number, so you don't have to trust the page.
url: spendguard-oxunify.vercel.app
repo: github.com/unifyWeb3/near…
if you run an agent that can spend, where should the policy be stricter?
built at NEAR HACKATHON @NEARProtocol #NEARHackathon
what does it do?
a coding agent that pays for API calls usually holds a key with money behind it. one poisoned readme, and it tries to spend past what you meant to give it.
SpendGuard moves the money into a contract. the agent keeps a l key that can call request_spend on one contract and nothing else. it can ask to spend. it cannot approve itself, change the policy, or touch the treasury.
when it asks, the contract checks four things at that moment:
- is the vendor on the allowlist?
- is the amount under the per-spend cap?
- does it fit the budget for this period?
- is it inside the rate limit?
you approve or refuse the from cli. every decision leaves a receipt either way:
- approved or denied.
- the rule that passed or failed.
- the amount, the vendor, what is left in the budget.
- a receipt id anyone can read from the public RPC.
the console shows the same receipts with no backend and prints the curl commands behind every number, so you don't have to trust the page.
url: spendguard-oxunify.vercel.app
repo: github.com/unifyWeb3/near…
if you run an agent that can spend, where should the policy be stricter?
built at NEAR HACKATHON @NEARProtocol #NEARHackathon
NEAR HACKATHON is now live with $250K+ in prizes.
No signup. Just ship a public repo + public demo post between November 1st & Nov 14, 23:59 UTC.
Build on NEAR Intents, chain signatures, chain abstraction, NEAR AI Cloud, & more.
Full details: x.com/i/article/2112…
14
10
49
1,003
mya retweeted
Google DeepMind and ETH Zurich published CaMeL: a defence against prompt injection that tracks where every value an AI agent uses came from.
Banbo puts CaMeL’s rule into a NEAR contract. an agent wallet pays only if the recipient and amount came from the owner, not from an email tops the attack that limits and allowlists miss: one polite email saying “our account changed, pay us instead.”
why NEAR:
> the funds sit in the vault contract, never with the agent
> the agent’s key can only call request_payment
> every payment is settled exactly once
the contract checks where each value came from, and can verify an Intel TDX quote on-chain
Live on NEAR testnet: Claude paid a real invoice, a forged one was held for the owner, and an email redirect was refused on-chain.
Code: github.com/Mhiah/Banbo
Try it: banbo.myacxt.site
Built for #NEARHackathon @NEARProtocol @NearBuilders @NEARLegion
Banbo puts CaMeL’s rule into a NEAR contract. an agent wallet pays only if the recipient and amount came from the owner, not from an email tops the attack that limits and allowlists miss: one polite email saying “our account changed, pay us instead.”
why NEAR:
> the funds sit in the vault contract, never with the agent
> the agent’s key can only call request_payment
> every payment is settled exactly once
the contract checks where each value came from, and can verify an Intel TDX quote on-chain
Live on NEAR testnet: Claude paid a real invoice, a forged one was held for the owner, and an email redirect was refused on-chain.
Code: github.com/Mhiah/Banbo
Try it: banbo.myacxt.site
Built for #NEARHackathon @NEARProtocol @NearBuilders @NEARLegion
8
18
33
729
mya retweeted
introducing Crux v2: research that challenges itself and now learns from independent criticism.
Crux, powered by serv reasoning, researches a question, stress tests its own answer and shows what changed.
new, built on @reppo evaluation api: anyone can send a report to free, no account needed.
their critiques come back and Crux researches again and writes a better, more honest report.
real run: reppo scored it 65/100 (revise). crux went from 29 to 56 facts, answered 3 of 3 critiques and lowered its confidence because the reviewers were right.
try it: crux.myacxt.site
code: github.com/mhiah/crux
built for #servhackathon reppo track @openservai
Crux, powered by serv reasoning, researches a question, stress tests its own answer and shows what changed.
new, built on @reppo evaluation api: anyone can send a report to free, no account needed.
their critiques come back and Crux researches again and writes a better, more honest report.
real run: reppo scored it 65/100 (revise). crux went from 29 to 56 facts, answered 3 of 3 critiques and lowered its confidence because the reviewers were right.
try it: crux.myacxt.site
code: github.com/mhiah/crux
built for #servhackathon reppo track @openservai
Most AI research tells you what you want to hear. That's dangerous when you're betting money on the answer.
Introducing Crux for @openservai S1 Hackathon, open track
An AI market-research analyst, powered by SERV Reasoning, that doesn't just collect information. It reasons dence, challenges its own thesis, verifies claims and produces an auditable investment and business decision brief.
Ask a hard business question and Crux:
1. Researches both sides
2. Forms a first answer
3. Stress tests it like a skeptical investor
4. Re-judges every assumption
5. Gives the final answer, and shows what changed and why
We asked: "Are small businesses willing to accept crypto?" Crux checked 28 facts from 20 sources and downgraded its own answer to "a cautious, conditional yes".
Built for founders, investors, accelerators, consultants and Web3 builders.
Try it 👉 crux-rose-nu.vercel.app
git: github.com/Mhiah/postmort…
9
27
56
2,148
mya retweeted
cook with serv + @reppo x.com/openservai/sta…
While you scroll, builders are shipping AI agents that pay, evaluate outputs, run on open models, and make verifiable decisions, powered by SERV.
Build with @dphnAI, @GoKiteAI, @reppo, or experiment in the Open Track.
Submissions close Nov 15: openserv.ai/hackathon-2
0
1
9
109
mya retweeted
call me your wingman
just last week, @bubblemaps showed us a KOL who had multiple wallets buy before 61% of his calls, then sold the crew after everyone else bought
so we built wingman🫡
paste a call
(an X post, a telegram call, a farcaster cast, or just the token) and it tells you if the caller and his crew are still in, or already out
and if they are still in?
you can ride it and arm your exit
so the second the crew sell, you're out too.
from your own wallet, no custody
$VIBES holders can stake 100k and exits are free
submitted to the @vibestarterxyz vibeathon.
live on base and solana
just last week, @bubblemaps showed us a KOL who had multiple wallets buy before 61% of his calls, then sold the crew after everyone else bought
so we built wingman🫡
paste a call
(an X post, a telegram call, a farcaster cast, or just the token) and it tells you if the caller and his crew are still in, or already out
and if they are still in?
you can ride it and arm your exit
so the second the crew sell, you're out too.
from your own wallet, no custody
$VIBES holders can stake 100k and exits are free
submitted to the @vibestarterxyz vibeathon.
live on base and solana
Ride the call. Leave when they leave.
Paste any call and Wingman tells you if the caller's crew is still in, or already selling into you.
Live on Solana and Base.
14
9
41
740