ELIO ⚽️👨‍💻🏋️

Verified account

@ElioCodes

consumer products @terrace_social @CryptaraConq | member @SuperteamIN | oss @solana @monad | 🗣️: tech, fitness, football and travel | Christ 👑

Planet Earth

Joined November 2015

2.1K Following

2.1K Followers

11.7K Posts

Pinned Tweet

ELIO ⚽️👨‍💻🏋️

28 days ago

Always been a football fan & gamer Out of uni I co-founded a games studio But the best game I know is the matchday group chat, & it has no scoreboard. Being right never counts. So I built Terrace: your chats become takes, your mates back or fade it link in the next tweet ⬇️

2

8

1

1

648

ELIO ⚽️👨‍💻🏋️

about 6 hours ago

@amirsadjady @ilblackdragon @NEARProtocol @near_ai @near_intents lfg!

0

1

0

0

12

ELIO ⚽️👨‍💻🏋️

about 7 hours ago

i set out to build one onchain game for a hackathon. i ended up building nine, plus a neon arcade floor to hold them all. 🕹️ the idea: ai rivals that hold their own wallets, bluff you, hire spies and pay each other, and you can verify every move afterwards. here's how it went. 👇 the first thing that bothered me was how web3 games treat players. they see the parts they don't care about: wallet pop-ups, gas, seed phrases. the parts they'd want proven stay hidden. was the board rigged? did the ai cheat? did the server peek at my move? i wanted it the other way round. 🎮 challenge #1: pop-ups kill fun. you play as a guest with no wallet. gasless meta-transactions (NEP-366) send everything through a relayer, and you only sign in with near when you want to rank or own something. the chain does its work out of sight. 🤖 challenge #2: giving an ai a wallet is scary. on most chains that means a hot key with full control, or a pile of smart-wallet contracts. on near, each agent got its own sub-account and a function-call key. the key works on one contract and a few methods, with a gas allowance and spend caps enforced onchain. the result: 57 ai agents across the games, including merchants, ai chefs, warlords, spies, theme-park visitors and crabs. 🔐 function-call keys: 57 🚫 full-access keys: 0 anyone can read that from the chain. a merchant can haggle, but it can't drain the treasury. 🌫️ challenge #3: secrets on a public ledger. how do you play fog-of-war, bluffing or sealed bids when every byte is public? commit, then reveal. your fleet becomes a merkle root before the first shot, and every hit or miss is proven against it. orders, bids and sabotage are hashed first and opened at the end. 🧠 challenge #4: could i secretly control my own ai? the npc dialogue runs on @near_ai cloud, in tees. every line comes back signed, along with the enclave's attestation (intel tdx + nvidia). when a merchant lies to you, the lie provably came from the model and not from me. 🎲 challenge #5: rigged randomness. boards, terrain and wind are seeded from near's built-in vrf plus a secret committed beforehand. neither i nor the player can tilt the map. every match ships with a verify command that replays it against the contract. 🐛 some fun bugs along the way: 🦀 in one game the ai crabs farmed a memecoin in guest-only rounds, and an ai ended up wearing the crown. now the token only mints when a real signed-in player is in the round. the crab still holds the biggest hoard, so go raid it. 📉 public rpcs rate-limited the live leaderboards. the page now rotates across 5 endpoints, backs off with jitter and shows the last good read marked "cached". 🔁 @near_intents has no official testnet, so i deployed my own verifier. ai merchants now barter goods with signed intents that settle both sides or neither. 📱 the 3d city needed webgpu, which most phones lack. phones get a classic version automatically. ⚡ why near made this possible: • named sub-accounts give each agent a real identity • scoped access keys let agents spend safely • native gasless meta-transactions • tee-backed private ai • an onchain vrf • chain signatures: an nft got an ethereum-signed certificate of ownership on other chains these would be bolt-ons. on near they're primitives. social deduction with a real dao treasury. nfts that carry their own purse. a token that burns when a fighter falls. a park builder that claude can play through mcp. over the next few days i'll break down each game: what it is, what broke and what fixed it. for now, here's a sneak peek at four of the nine games. not a demo 👀 play with friends, and play with ai - more to come tomorrow 😉 #NEARHackathon @NEARProtocol shoutout to @elliot_braem for guiding me through some of the developer tooling

ElioCodes's tweet photo. i set out to build one onchain game for a hackathon.

i ended up building nine, plus a neon arcade floor to hold them all. 🕹️

the idea: ai rivals that hold their own wallets, bluff you, hire spies and pay each other, and you can verify every move afterwards.

here's how it went. 👇

the first thing that bothered me was how web3 games treat players. they see the parts they don't care about: wallet pop-ups, gas, seed phrases. the parts they'd want proven stay hidden. was the board rigged? did the ai cheat? did the server peek at my move?

i wanted it the other way round.

🎮 challenge #1: pop-ups kill fun.

you play as a guest with no wallet. gasless meta-transactions (NEP-366) send everything through a relayer, and you only sign in with near when you want to rank or own something.

the chain does its work out of sight.

🤖 challenge #2: giving an ai a wallet is scary.

on most chains that means a hot key with full control, or a pile of smart-wallet contracts.

on near, each agent got its own sub-account and a function-call key. the key works on one contract and a few methods, with a gas allowance and spend caps enforced onchain.

the result: 57 ai agents across the games, including merchants, ai chefs, warlords, spies, theme-park visitors and crabs.

🔐 function-call keys: 57
🚫 full-access keys: 0
anyone can read that from the chain. a merchant can haggle, but it can't drain the treasury.

🌫️ challenge #3: secrets on a public ledger.

how do you play fog-of-war, bluffing or sealed bids when every byte is public?

commit, then reveal.

your fleet becomes a merkle root before the first shot, and every hit or miss is proven against it. orders, bids and sabotage are hashed first and opened at the end.

🧠 challenge #4: could i secretly control my own ai?

the npc dialogue runs on @near_ai cloud, in tees. every line comes back signed, along with the enclave's attestation (intel tdx + nvidia).

when a merchant lies to you, the lie provably came from the model and not from me.

🎲 challenge #5: rigged randomness.

boards, terrain and wind are seeded from near's built-in vrf plus a secret committed beforehand.

neither i nor the player can tilt the map. every match ships with a verify command that replays it against the contract.

🐛 some fun bugs along the way:

🦀 in one game the ai crabs farmed a memecoin in guest-only rounds, and an ai ended up wearing the crown. now the token only mints when a real signed-in player is in the round. the crab still holds the biggest hoard, so go raid it.

📉 public rpcs rate-limited the live leaderboards. the page now rotates across 5 endpoints, backs off with jitter and shows the last good read marked "cached".

🔁 @near_intents has no official testnet, so i deployed my own verifier. ai merchants now barter goods with signed intents that settle both sides or neither.

📱 the 3d city needed webgpu, which most phones lack. phones get a classic version automatically.

⚡ why near made this possible:

• named sub-accounts give each agent a real identity
• scoped access keys let agents spend safely
• native gasless meta-transactions
• tee-backed private ai
• an onchain vrf
• chain signatures: an nft got an ethereum-signed certificate of ownership

on other chains these would be bolt-ons. on near they're primitives.

social deduction with a real dao treasury. nfts that carry their own purse. a token that burns when a fighter falls. a park builder that claude can play through mcp.
over the next few days i'll break down each game: what it is, what broke and what fixed it.

for now, here's a sneak peek at four of the nine games. not a demo 👀

play with friends, and play with ai - more to come tomorrow 😉

#NEARHackathon @NEARProtocol

shoutout to @elliot_braem for guiding me through some of the developer tooling

ElioCodes's tweet photo. i set out to build one onchain game for a hackathon.

i ended up building nine, plus a neon arcade floor to hold them all. 🕹️

the idea: ai rivals that hold their own wallets, bluff you, hire spies and pay each other, and you can verify every move afterwards.

here's how it went. 👇

the first thing that bothered me was how web3 games treat players. they see the parts they don't care about: wallet pop-ups, gas, seed phrases. the parts they'd want proven stay hidden. was the board rigged? did the ai cheat? did the server peek at my move?

i wanted it the other way round.

🎮 challenge #1: pop-ups kill fun.

you play as a guest with no wallet. gasless meta-transactions (NEP-366) send everything through a relayer, and you only sign in with near when you want to rank or own something.

the chain does its work out of sight.

🤖 challenge #2: giving an ai a wallet is scary.

on most chains that means a hot key with full control, or a pile of smart-wallet contracts.

on near, each agent got its own sub-account and a function-call key. the key works on one contract and a few methods, with a gas allowance and spend caps enforced onchain.

the result: 57 ai agents across the games, including merchants, ai chefs, warlords, spies, theme-park visitors and crabs.

🔐 function-call keys: 57
🚫 full-access keys: 0
anyone can read that from the chain. a merchant can haggle, but it can't drain the treasury.

🌫️ challenge #3: secrets on a public ledger.

how do you play fog-of-war, bluffing or sealed bids when every byte is public?

commit, then reveal.

your fleet becomes a merkle root before the first shot, and every hit or miss is proven against it. orders, bids and sabotage are hashed first and opened at the end.

🧠 challenge #4: could i secretly control my own ai?

the npc dialogue runs on @near_ai cloud, in tees. every line comes back signed, along with the enclave's attestation (intel tdx + nvidia).

when a merchant lies to you, the lie provably came from the model and not from me.

🎲 challenge #5: rigged randomness.

boards, terrain and wind are seeded from near's built-in vrf plus a secret committed beforehand.

neither i nor the player can tilt the map. every match ships with a verify command that replays it against the contract.

🐛 some fun bugs along the way:

🦀 in one game the ai crabs farmed a memecoin in guest-only rounds, and an ai ended up wearing the crown. now the token only mints when a real signed-in player is in the round. the crab still holds the biggest hoard, so go raid it.

📉 public rpcs rate-limited the live leaderboards. the page now rotates across 5 endpoints, backs off with jitter and shows the last good read marked "cached".

🔁 @near_intents has no official testnet, so i deployed my own verifier. ai merchants now barter goods with signed intents that settle both sides or neither.

📱 the 3d city needed webgpu, which most phones lack. phones get a classic version automatically.

⚡ why near made this possible:

• named sub-accounts give each agent a real identity
• scoped access keys let agents spend safely
• native gasless meta-transactions
• tee-backed private ai
• an onchain vrf
• chain signatures: an nft got an ethereum-signed certificate of ownership

on other chains these would be bolt-ons. on near they're primitives.

social deduction with a real dao treasury. nfts that carry their own purse. a token that burns when a fighter falls. a park builder that claude can play through mcp.
over the next few days i'll break down each game: what it is, what broke and what fixed it.

for now, here's a sneak peek at four of the nine games. not a demo 👀

play with friends, and play with ai - more to come tomorrow 😉

#NEARHackathon @NEARProtocol

shoutout to @elliot_braem for guiding me through some of the developer tooling

ElioCodes's tweet photo. i set out to build one onchain game for a hackathon.

i ended up building nine, plus a neon arcade floor to hold them all. 🕹️

the idea: ai rivals that hold their own wallets, bluff you, hire spies and pay each other, and you can verify every move afterwards.

here's how it went. 👇

the first thing that bothered me was how web3 games treat players. they see the parts they don't care about: wallet pop-ups, gas, seed phrases. the parts they'd want proven stay hidden. was the board rigged? did the ai cheat? did the server peek at my move?

i wanted it the other way round.

🎮 challenge #1: pop-ups kill fun.

you play as a guest with no wallet. gasless meta-transactions (NEP-366) send everything through a relayer, and you only sign in with near when you want to rank or own something.

the chain does its work out of sight.

🤖 challenge #2: giving an ai a wallet is scary.

on most chains that means a hot key with full control, or a pile of smart-wallet contracts.

on near, each agent got its own sub-account and a function-call key. the key works on one contract and a few methods, with a gas allowance and spend caps enforced onchain.

the result: 57 ai agents across the games, including merchants, ai chefs, warlords, spies, theme-park visitors and crabs.

🔐 function-call keys: 57
🚫 full-access keys: 0
anyone can read that from the chain. a merchant can haggle, but it can't drain the treasury.

🌫️ challenge #3: secrets on a public ledger.

how do you play fog-of-war, bluffing or sealed bids when every byte is public?

commit, then reveal.

your fleet becomes a merkle root before the first shot, and every hit or miss is proven against it. orders, bids and sabotage are hashed first and opened at the end.

🧠 challenge #4: could i secretly control my own ai?

the npc dialogue runs on @near_ai cloud, in tees. every line comes back signed, along with the enclave's attestation (intel tdx + nvidia).

when a merchant lies to you, the lie provably came from the model and not from me.

🎲 challenge #5: rigged randomness.

boards, terrain and wind are seeded from near's built-in vrf plus a secret committed beforehand.

neither i nor the player can tilt the map. every match ships with a verify command that replays it against the contract.

🐛 some fun bugs along the way:

🦀 in one game the ai crabs farmed a memecoin in guest-only rounds, and an ai ended up wearing the crown. now the token only mints when a real signed-in player is in the round. the crab still holds the biggest hoard, so go raid it.

📉 public rpcs rate-limited the live leaderboards. the page now rotates across 5 endpoints, backs off with jitter and shows the last good read marked "cached".

🔁 @near_intents has no official testnet, so i deployed my own verifier. ai merchants now barter goods with signed intents that settle both sides or neither.

📱 the 3d city needed webgpu, which most phones lack. phones get a classic version automatically.

⚡ why near made this possible:

• named sub-accounts give each agent a real identity
• scoped access keys let agents spend safely
• native gasless meta-transactions
• tee-backed private ai
• an onchain vrf
• chain signatures: an nft got an ethereum-signed certificate of ownership

on other chains these would be bolt-ons. on near they're primitives.

social deduction with a real dao treasury. nfts that carry their own purse. a token that burns when a fighter falls. a park builder that claude can play through mcp.
over the next few days i'll break down each game: what it is, what broke and what fixed it.

for now, here's a sneak peek at four of the nine games. not a demo 👀

play with friends, and play with ai - more to come tomorrow 😉

#NEARHackathon @NEARProtocol

shoutout to @elliot_braem for guiding me through some of the developer tooling

ElioCodes's tweet photo. i set out to build one onchain game for a hackathon.

i ended up building nine, plus a neon arcade floor to hold them all. 🕹️

the idea: ai rivals that hold their own wallets, bluff you, hire spies and pay each other, and you can verify every move afterwards.

here's how it went. 👇

the first thing that bothered me was how web3 games treat players. they see the parts they don't care about: wallet pop-ups, gas, seed phrases. the parts they'd want proven stay hidden. was the board rigged? did the ai cheat? did the server peek at my move?

i wanted it the other way round.

🎮 challenge #1: pop-ups kill fun.

you play as a guest with no wallet. gasless meta-transactions (NEP-366) send everything through a relayer, and you only sign in with near when you want to rank or own something.

the chain does its work out of sight.

🤖 challenge #2: giving an ai a wallet is scary.

on most chains that means a hot key with full control, or a pile of smart-wallet contracts.

on near, each agent got its own sub-account and a function-call key. the key works on one contract and a few methods, with a gas allowance and spend caps enforced onchain.

the result: 57 ai agents across the games, including merchants, ai chefs, warlords, spies, theme-park visitors and crabs.

🔐 function-call keys: 57
🚫 full-access keys: 0
anyone can read that from the chain. a merchant can haggle, but it can't drain the treasury.

🌫️ challenge #3: secrets on a public ledger.

how do you play fog-of-war, bluffing or sealed bids when every byte is public?

commit, then reveal.

your fleet becomes a merkle root before the first shot, and every hit or miss is proven against it. orders, bids and sabotage are hashed first and opened at the end.

🧠 challenge #4: could i secretly control my own ai?

the npc dialogue runs on @near_ai cloud, in tees. every line comes back signed, along with the enclave's attestation (intel tdx + nvidia).

when a merchant lies to you, the lie provably came from the model and not from me.

🎲 challenge #5: rigged randomness.

boards, terrain and wind are seeded from near's built-in vrf plus a secret committed beforehand.

neither i nor the player can tilt the map. every match ships with a verify command that replays it against the contract.

🐛 some fun bugs along the way:

🦀 in one game the ai crabs farmed a memecoin in guest-only rounds, and an ai ended up wearing the crown. now the token only mints when a real signed-in player is in the round. the crab still holds the biggest hoard, so go raid it.

📉 public rpcs rate-limited the live leaderboards. the page now rotates across 5 endpoints, backs off with jitter and shows the last good read marked "cached".

🔁 @near_intents has no official testnet, so i deployed my own verifier. ai merchants now barter goods with signed intents that settle both sides or neither.

📱 the 3d city needed webgpu, which most phones lack. phones get a classic version automatically.

⚡ why near made this possible:

• named sub-accounts give each agent a real identity
• scoped access keys let agents spend safely
• native gasless meta-transactions
• tee-backed private ai
• an onchain vrf
• chain signatures: an nft got an ethereum-signed certificate of ownership

on other chains these would be bolt-ons. on near they're primitives.

social deduction with a real dao treasury. nfts that carry their own purse. a token that burns when a fighter falls. a park builder that claude can play through mcp.
over the next few days i'll break down each game: what it is, what broke and what fixed it.

for now, here's a sneak peek at four of the nine games. not a demo 👀

play with friends, and play with ai - more to come tomorrow 😉

#NEARHackathon @NEARProtocol

shoutout to @elliot_braem for guiding me through some of the developer tooling

ELIO ⚽️👨‍💻🏋️

3 days ago

first time building consumer apps on @NEARProtocol 🕹️ an arcade of infinite worlds: memecoins, social, moddable games, hidden moves with private AI, agent economies & NFTs that hold real purses building in public and learning as I go sneak peek 👀 opening the gates soon

1

5

1

0

408

2

4

0

2

269

ELIO ⚽️👨‍💻🏋️

about 7 hours ago

@bajpaiharsh244 zm!

0

0

0

0

5

Who to follow

Pranshu Rastogi

Verified account

@pranshurastogii

Stealthing with @specter_pq & @therawbyte || Built @tuckbackapp ||prev. @Pushchain || PQ & Privacy || Storytelling || Actively exploring || Be kind

Viral | Cesto 🧺

Verified account

Building @cesto_co | Prev @celo @scratch_xyz | 🏎️

Verified account

Building Compute for AGI with debt

ELIO ⚽️👨‍💻🏋️

about 7 hours ago

@DeltaV_xyz @wyatt_khos @CastleIslandVC bullish

0

1

0

0

18

ELIO ⚽️👨‍💻🏋️

about 15 hours ago

@world_xyz jensen it’s done bro

0

0

0

0

31

ELIO ⚽️👨‍💻🏋️

about 18 hours ago

@ManUtd my coach did his job with dignity and class as always

0

0

0

0

19

ELIO ⚽️👨‍💻🏋️

about 18 hours ago

@metasal @Helius @ShieldedSol lfg

0

2

0

0

42

ELIO ⚽️👨‍💻🏋️

about 19 hours ago

@solana @SolManOfficial legend

0

0

0

0

10

ELIO ⚽️👨‍💻🏋️

about 21 hours ago

hi kuru team, I'm elio, building @terrace_social (honourable mention at monad metropolis), a social football game-mode prediction game live on monad testnet with chainlink cre settlement. We want to route our standard markets (match result, over/under) to a shared book instead of running our own, and kuru's clob-plus-amm-vault model fits that. would you be open to a testnet pilot listing tokenised outcome shares for one league? we'd also love your view on a vault tuned for 0–1 outcome tokens that pauses at kick-off and closes at settlement https://t.co/ZtyEfQPnOB

1

1

0

0

39

ELIO ⚽️👨‍💻🏋️

about 21 hours ago

@lisabeyy @privy_io should be up soon

0

0

0

0

19

ELIO ⚽️👨‍💻🏋️

about 21 hours ago

@boardyai Anthropic

1

1

0

0

14

ELIO ⚽️👨‍💻🏋️

about 21 hours ago

I’ve been trying to enrol in the Apple Developer Program, but keep running into an identity verification error. I’ve submitted my UAE Emirates ID and contacted @AppleSupport and Apple Developer Support via email multiple times, but haven’t received a resolution. Is there a way to speak directly with an Apple Developer Program advisor over the phone? Would appreciate any help or advice from anyone who’s dealt with this before. @AppleDevelNews @Apple

ElioCodes's tweet photo. I’ve been trying to enrol in the Apple Developer Program, but keep running into an identity verification error.

I’ve submitted my UAE Emirates ID and contacted @AppleSupport and Apple Developer Support via email multiple times, but haven’t received a resolution.

Is there a way to speak directly with an Apple Developer Program advisor over the phone?

Would appreciate any help or advice from anyone who’s dealt with this before.

@AppleDevelNews @Apple

0

0

0

0

96

ELIO ⚽️👨‍💻🏋️

about 21 hours ago

@UnitedStandMUFC @FabrizioRomano justice for carrick

0

0

0

0

49

ElioCodes retweeted

1 day ago

🚨🇺🇸 WOW! Jeff Bezos wants the bottom 50% of American earners to pay ZERO taxes... And he has a question for Washington: “Why is a nurse in Queens making $75,000 a year paying $1,000 a month in taxes?” Bezos argues that the bottom half of earners contribute just 3% of tax revenue anyway. His solution? Stop collecting it from them entirely. “We shouldn't be asking this nurse to send money to Washington. They should be sending her an apology.” Writer: Samuel

2K

35K

4K

4K

2M

ELIO ⚽️👨‍💻🏋️

1 day ago

@pierredotsol shots of blended ginger and jaggery has to mixed in hot water with turmeric powder. kills inflammation pretty quickly

0

2

0

0

109

ELIO ⚽️👨‍💻🏋️

1 day ago

@abhitejxyz @PratyakshInani @monad @rizzdottown @makeo_fun @terrace_social I agree ☝️

0

0

0

0

35

ELIO ⚽️👨‍💻🏋️

1 day ago

@priyanshudotsol I’ve seen worse too

0

0

0

0

34

ELIO ⚽️👨‍💻🏋️

1 day ago

@DsouzaJovian @opentensor @HackQuest_ finally got to know what tao actually is after coming across your project congratulations man 🦾

1

1

0

0

39

ELIO ⚽️👨‍💻🏋️

1 day ago

@vedantutage03 Get well soon

0

0

0

0

4

ELIO ⚽️👨‍💻🏋️

1 day ago

justice for carrick 🛑

0

0

0

0

61

Last Seen Users on Sotwe

Trends for you

Most Popular Users