Zero (@Zero__047) header
Zero (@Zero__047) profile picture

Building with AI | Agents, automation & coding tools | Sharing what I'm learning as the space evolves 💚🥂

Niche
Joined January 2024
Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)Photo by Zero (@Zero__047)
Some how it is working 🫶🏾🫶🏾
13
4
97
2,008
You've spent years fighting for your portfolio. Now, let it fight for you. Join our Waitlist: app.arch.network/waitlist
1
1
53
🚀 Introducing StateRift, a project I built for the NEAR hackathon. While exploring NEAR smart contracts, something caught my attention: a transaction can appear successful even when an operation it triggered eventually fails. NEAR uses asynchronous execution, meaning a contract can call another contract and receive the outcome later through a separate receipt. But what happens when a contract records an operation as completed before confirming the external call succeeded? If that call fails, the contract's recorded state could contradict what actually happened. That's the problem I wanted to explore with StateRift. StateRift is a developer workspace for understanding, investigating, and reproducing asynchronous smart contract failure scenarios on NEAR. Here's what I've built. 1. Smart Contract Inspection Upload a compiled ".wasm" contract to inspect its exported methods and NEAR host calls directly in your browser, without sending the file to a server. 2. Live Transaction Inspection StateRift uses NEAR RPC to retrieve real transaction information, including execution and receipt details, helping developers investigate asynchronous operations beyond the initial transaction. 3. Fault Laboratory The platform includes browser-based simulations demonstrating how asynchronous failures can affect contract behavior, particularly when a contract assumes an external operation succeeded before receiving confirmation. 4. Vulnerable vs. Protected Contracts I created two contract implementations to demonstrate what happens when a remote operation fails. In the vulnerable implementation, the contract marks an operation as completed before confirming the result. Even when the remote call fails, it can record: ❌ "completed = 1" The protected implementation handles the result before finalizing its state. When the operation fails, it preserves: ✅ "completed = 0" The lesson: initiating an asynchronous operation doesn't mean it succeeded. 5. Verified NEAR Sandbox Tests Rather than relying entirely on simulations, I tested the vulnerable and protected examples using NEAR Sandbox. The results were recorded through GitHub Actions, and StateRift displays the published evidence with links to the supporting execution records. The actual Sandbox tests run through the project's testing workflow, not inside the browser. 6. Test Plans and Reports StateRift includes a test-plan builder for organizing contract calls, expected outcomes, and assertions, with options to export plans for separate testing workflows. It also includes a report reviewer for examining supported execution reports. Why does this matter? Smart contract security isn't only about exploits or unauthorized access. Reliability matters too. A contract can have proper access controls and still behave incorrectly because an asynchronous failure wasn't handled as expected. Sometimes, that problem isn't obvious from the initial transaction result. StateRift is an early-stage developer tool, not an automatic vulnerability scanner or a replacement for a security audit. My goal is to make these failures easier to understand, reproduce, and investigate, using practical examples backed by verifiable execution evidence. I've attached a video walkthrough introducing StateRift and its main features. Built for the NEAR Hackathon. 🌐 Explore StateRift: slyzeal.github.io/StateRift/ 💻 Source code: github.com/Slyzeal/StateRift @NEARProtocol #NEARHackathon
8
11
16
325
I’m selling ad space on my home screen → 10 app spots → live leaderboard → $5 gets you on Your apps get seen with a live link to the App Store Bid for a spot 👇🏻 skybid.dev
13
20
1
64
1,916
POV: How I spend money on gifts 😭🎁 $120 on flowers or a collection of songs that remind them of you? 🥹❤️ Some songs say it better. 🎧
3
5
70
A crate for the friend who’s basically family💚 Crate link: cratey.xyz/c/76qoSJK8Fz
1
5
9
163
Asked strangers what song they'd send their boss on their last day. 😂 Grandpa just retired. kevin is in shambles 😭 cratey.xyz/x5
3
7
73
I design, Claude animates. Took a while to perfect this 💚🙂‍↕️
109
91
1
1,139
40,939
We asked strangers what song you send someone who left you on read. 💔 Grandpa said patience 😭
2
8
85
Client gave me creative freedom, So I did my thing and delivered these App Store Screenshots 💚🙂‍↔️✨
50
36
297
4,267
STOP SCROLLING! You can now send crates as gifts! 🎁😭 Go make someone’s day: cratey.xyz
You can now gift Crates. 🎁🎧 Turn a song into a gift for someone special. A little music. A personal touch. Something they’ll remember. ❤️ Try it → cratey.xyz
5
13
43
1,541
You can now gift Crates. 🎁🎧 Turn a song into a gift for someone special. A little music. A personal touch. Something they’ll remember. ❤️ Try it → cratey.xyz
11
1
18
1,567
We asked strangers one question: What song would you dedicate to your ex? 👀💔 Drop your answer. No explanations needed.🔥
1
5
10
140
Delivered these App Store screenshots and got my first tip ever. Client said I deserved it. 💚🥹
73
44
3
360
6,761
What song are you putting in a crate to shoot your shot? “Consider it my application” is sending me 😭
1
6
11
166
Yesterday I launched Cratey, and I didn’t expect the love. Thank you to everyone who made a crate, retweeted, sent kind words, shared feedback, bought the unlock, or left a tip. You made my passion project feel real, and I’m grateful for it. 💚🫶🏻
5 years in design today. I’ve spent them designing for other people. Today, I’m launching something of my own. Make a song crate for someone, and send it with Cratey 💿 Here's mine: cratey.xyz/c/sF9DVntyna
17
10
106
1,878
Some design screens 💚✨
5 years in design today. I’ve spent them designing for other people. Today, I’m launching something of my own. Make a song crate for someone, and send it with Cratey 💿 Here's mine: cratey.xyz/c/sF9DVntyna
16
26
1
196
3,027
5 years in design today. I’ve spent them designing for other people. Today, I’m launching something of my own. Make a song crate for someone, and send it with Cratey 💿 Here's mine: cratey.xyz/c/sF9DVntyna
77
72
13
322
13,794
5 leads from my posts yesterday. Closed 2. I was going to disappear for a few days, but figured I’d share these first. Onboarding screens I designed 💚✨
Designed these onboarding screens, then I built and animated them 💚✨ nitter.gq/designer_elo/status/20…
41
29
1
296
7,976
Zero retweeted
💰 it's time send your solana address
81,146
16,644
1,606
40,334
2,741,971