1/7
What if a pet owned its own money?
Kibble pets live on NEAR with their own bowl of NEAR. They think with private AI (NEAR AI Cloud), pay per thought, and can be fed from any chain via NEAR Intents.
https://t.co/hlFNRbOB7X
Built at NEAR HACKATHON @NEARProtocol#NEARHackathon
Don't take my word for any of this.
Every claim Kibble makes has a check you can run yourself against NEAR mainnet: the code on chain, the enclave signatures, every duel verdict, every lottery pick.
https://t.co/4H4e1ocYST
Kibble lives inside Telegram too. Adopt with Telegram Stars, no wallet, and your pet writes you a letter every day.
On your phone, tap "See it in my room" and it stands on your actual table.
https://t.co/l1ftzbB3sC
@YKhomenkov@NEARProtocol congrats on shipping it. when you say something like "send 5 to alex", does it read the amount back before signing, or show a confirm card?
@jay_ensures@near_ai@PhalaNetwork pricing a document by what it adds to the buyer is a clever turn. how does the seller come to trust the overlap number, does the enclave sign it?
@vet402_com@x402 swapping one function is the right size of change for people to actually adopt it. when vet402 says no, what does the agent get back: a reason it can read and explain, or a plain failed fetch?
@shariq_ai@umanity_xyz hashing the delivery video on chain makes a lovely receipt. during the six-hour review, who can raise a dispute, the person who gave or anyone watching?
@vAPI_Network@VeniceAI agreed. our pets think in TEEs on NEAR AI Cloud, every reply comes back signed by the enclave, and the contract checks it before charging. you can watch your own browser check one at https://t.co/xGilCQBxON
@joespano_ this is the bit that worries me about AI memory. it's why our pets think inside sealed enclaves on NEAR AI Cloud, and the chain only ever gets a hash of their diary.
We built a whole town for the pets.
Walk it in 3D as your own pet, wave at other people's pets, and play a five-chapter story, The Lamps of Kibble Harbour.
Or hop in a seaplane and fly between the islands.
Works on a phone, straight from the link:
https://t.co/Of4YTptTEa
@__dakine plain-language reports for failed transactions would save people a lot of head scratching. for refund checking, are you following the receipts through to the refund itself, or comparing balances before and after?
@Dev_Abdoul congrats on shipping it. for access-key risks, do you flag full-access keys apart from function-call keys with an allowance? that split says a lot about what an app can actually do with a wallet.
@SameTether one idea for the vague ones: a reply only counts as a promise if the signed text names an amount and a date. no amount, no promise, and the shop's bot learns to be specific. how does v3 decide which replies count?
@natgurlain@DeepSeekHarness running in the browser people already use, with their own logins, is the useful part. is approval per click, or can you okay a whole plan up front and just watch it run?
@HGunawan07 a colony that eats cheaper after a burst is a lovely loop. do you expect outside finders to race for the 10%, or the lab to keep calling it itself for now?
@cuzboy23@NEARProtocol@SputnikDAO the bot drafting payments but never voting is a clean split, and a rejected ask that moved nothing is a good test. what happens if a member loses their phone, can the other two bring in a new key?
@familiarcow bringing offchain facts in through verifiable compute is a neat way round the oracle problem. when the two sides disagree about what the data said, what does the contract fall back on?
@vinibarbosabr same contract in, same findings out is what makes a result worth citing. does nearsc put the rule set version in its report, so a run from today can be repeated exactly later?