Heisbei (@Heisbei02) header
Heisbei (@Heisbei02) profile picture

Developer ⭐️

Joined August 2024
Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)Photo by Heisbei (@Heisbei02)
Heisbei retweeted
9pm, raining, and you've just finished your 10th delivery of the day. soaked, phone on 4%. you open the app and today's pay is $12 less than yesterday, same route, same hours. you message support and get the answer every rider, driver and freelancer has heard before: "the system decided." millions of gig workers get paid by a formula they've never seen. base pay, distance rates, bonuses and fees all get calculated inside a server nobody can look at, and when it changes there's no notice and no way to check. you either trust it or argue in a support chat you won't win. so here's an app i'd love to see on @XLayerOfficial with @TapeOutWorld: fare & square. the platform publishes its pay formula as a tapeout circuit on x layer, and every payout comes with a receipt showing your inputs, the circuit id and the result. anyone can replay that receipt on the same circuit and get the exact same number. tapeout circuits are deterministic, so the worker, the platform and a regulator all land on the same answer. if the formula changes, it shows up onchain as a new version, so a pay cut can't slip in quietly. it's also more doable than it sounds. the core formula is fixed-point math in a small composable circuit, and a platform can start with a simplified version and build up from there. payroll itself doesn't need to run onchain. the public netlist and the replay are what matter. who it helps: • riders and drivers, who can dispute a deduction with proof instead of screenshots • platforms dealing with regulators. the eu platform work directive and similar rules are already pushing for algorithmic pay transparency, and this gives them something they can actually show • workers comparing apps before signing up • smaller platforms and worker-owned apps, since being open about pay is an easy way to stand out against the big players free for workers. platforms pay for a verifiable "fair pay" badge, ready-made regulator reports, and a listing on a public dashboard that compares formulas across apps. here's what a receipt could look like: pay = ($2.50 base + $0.80/km × 6km) × 1.2 rain surge = $8.76 replay it a hundred times and you'll still get $8.76. and if a platform's formula really is fair, proving it costs them nothing.
Good ideas deserve to be heard. Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT. Ends Nov 17. Submit here: bit.ly/4eQxFIH
4
10
23
396
Heisbei retweeted
one of the biggest challenges in digital hardware design is proving that you actually know how to design and build working circuits. 🧵 🖊️ imagine you’re applying for an embedded systems or digital design role. a company gives you a take-home test, you complete it, submit your work, and someone manually reviews it. the problem is that the result stays private. there’s no easy way for another company, instructor, or reviewer to independently verify that your design works. the same problem exists in education and within the tapeout ecosystem. students submit simulation screenshots, developers share github repositories, and builders showcase their circuits, but verifying the actual work can still be difficult. there’s also a problem with open competitions. since @TapeOutWorld makes circuit designs public when they’re submitted, someone can simply wait for another person to publish a working solution and copy it. so how do you reward the person who actually committed to solving a challenge first? my idea as a solution: circuitcred circuitcred is a sealed hardware design challenge and verification platform built on @TapeOutWorld and @XLayerOfficial it allows anyone to create a hardware design challenge, invite others to solve it, and verify who submitted a working solution before the deadline. think of it as a coding assessment platform, but for hardware and digital circuit design. the difference is that @XLayerOfficial handles the commitment and verification process. every successful submission gets a public, verifiable record that anyone can inspect without connecting a wallet. how circuitcred works the entire process has four stages. ->publish a challenge a company, instructor, or community organizer creates a challenge. for example: “design an 8-bit ALU with carry and zero flags, using no more than 120 gates.” the host defines the requirements, test cases, gate limit, submission deadline, and reveal deadline. the challenge is published through the host’s own DeWEB container. ->commit your solution participants read the requirements and start designing their circuits. they can use the tapeout canvas or write their designs in Verilog and compile them using TapeSynth. before the submission deadline, each participant submits a cryptographic hash of their design. this is important because the actual circuit remains hidden. nobody can see or copy another participant’s solution at this stage. participants can update their commitment before the deadline, but only their final commitment counts. ->reveal and verify once the commitment deadline passes, participants can reveal their designs. they tape out their circuits and submit the information needed to match the original commitment. the smart contract checks several things: -does the participant own the submitted circuit? -does the circuit match the hash they committed to earlier? -is the circuit within the allowed gate limit? -does it pass the required test cases? -does the submission meet the challenge requirements? the contract checks a sample of test cases directly on-chain. the full test suite is then independently executed using the TAP-02 reference evaluator. if the checks pass, the participant receives a successful on-chain record. ->public verification this is where circuitcred becomes useful beyond the competition itself. anyone can open a submission record without connecting a wallet or creating an account. they can see: >the challenge and its requirements >the solver’s wallet address >the circuit submitted >the number of gates used >the original commitment block >the reveal block >whether the design passed verification the browser independently runs the full test suite and checks the result against the blockchain. this gives reviewers a way to verify the result themselves instead of relying on screenshots or someone’s word.
Good ideas deserve to be heard. Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT. Ends Nov 17. Submit here: bit.ly/4eQxFIH
8
29
1
50
1,491
Heisbei retweeted
What if group challenges had rules that couldn’t be changed later? Right now when people do challenges together (fitness, study, savings, creative contests, etc.), the person who started it can quietly change the rules, scoring, or deadlines whenever they want. Everyone else just has to trust them. TapeOut circuits could stop that. When the challenge starts, the exact rules get locked into a circuit. After that, nobody can change how winners are decided or how progress is measured. Anyone can check the rules anytime and see that the results are fair. No more “the rules changed” excuses. Would actually want this on @XLayerOfficial @TapeOutWorld
61
3
63
392
Heisbei retweeted
What if API providers had to put money behind their uptime promises? Every API has a status page that says 99.9%. Every SaaS has an SLA. And when it actually goes down, you open a ticket, wait, and maybe get a credit three weeks later if you ask nicely. A Thread 🧵
Good ideas deserve to be heard. Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT. Ends Nov 17. Submit here: bit.ly/4eQxFIH
3
2
5
112
Heisbei retweeted
“There's no bank in the world that could do that.” Rebecca Rettig, COO & CLO of Jito Labs, on Binance's response to its $6B hack. Beyond the market impact, she highlights how exchanges, stablecoin issuers and other players came together to help identify and stop bad actors. The response to a crisis can reveal a lot about how an industry works.
10
11
23
513
Heisbei retweeted
Looking across the 400+ processors deployed on @XLayerOfficial and @TapeOutWorld right now, we already have all the raw primitives for an app I really wish existed onchain: PRESSOR (Printing Press + TapeOut Processor): an onchain Substack and liquid subscription protocol built on DeWEB, TapeSend, and TapeOut circuits. The problem it solves Independent writers, onchain analysts, and alpha researchers are stuck between two bad options: - Web2 platforms (Substack, Patreon, Ghost) take 10% to 30% once you add Stripe fees, freeze payouts in half the world, and can deplatform you overnight. - Paid Telegram or Discord groups leak within 10 seconds because one forwarding bot scrapes the whole channel. - Worse for readers: if you pay 120 USDT for an annual research pass and stop reading after 3 months, your remaining 9 months are a dead sunk cost. How Pressor works on X Layer TapeOut - Public Storefront on DeWEB (tape://): Writers publish free essays and previews directly to X Layer SiteRegistry (#id.2.cpu.tape), verified byte-for-byte via TapeKit SHA-256 with $0 monthly server bills. - Encrypted Paid Issues via TapeSend (TAP-10): Full research reports, PDFs, and alpha alerts are encrypted (X25519 + XChaCha20-Poly1305) and delivered through DeWebHub straight into active subscribers' containers. No email servers, no leaked invite links. - Subscriber Covenant Circuits (NAND + LATCH + REF): Each publication tapes out its pricing and loyalty rules as an immutable circuit. LATCH state tracks consecutive renewal streaks via step() to unlock archive tiers, while REF lets multiple writers wire their circuits into a joint bundle pass at zero transistor burn. - Liquid Second-Hand Subscriptions (ERC-6551 + Circuit Market): Because a subscription lives inside a TapeOut ERC-6551 container, a reader who buys a 1-year pass and leaves after 4 months can resell their container on the X Layer Circuit Market. Future TapeSend issues automatically route to the new holder, and the writer earns a secondary royalty. Who it is for & concrete use cases - Onchain Analysts & Research Writers: Sell 10 USDT/mo or 100 USDT/yr newsletters settled natively on X Layer, where readers actually buy annual passes because they know they can resell unused time. - Multi-Author Research Co-ops: Three independent X Layer analysts compose their publication circuits via REF into one "Ecosystem Pro Pass" that splits USDT revenue atomically on checkout. - Security Researchers & Dev Tool Maintainers: Ship time-sensitive vulnerability advisories and patch notes end-to-end encrypted to verified client containers over TapeSend. We have DeWEB for permanent pages, TapeSend for encrypted container mail, and ERC-6551 containers for transferable state. Putting them together turns subscriptions from sunk costs into liquid onchain assets. Would you pay more upfront for an annual research or alpha subscription if you could resell the remaining months onchain whenever you wanted?
Good ideas deserve to be heard. Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT. Ends Nov 17. Submit here: bit.ly/4eQxFIH
17
9
44
1,187
I would like to see a CircuitPack circuit packages that another builder can actually trust and reuse exist onchain. @TapeOutWorld already provides a canvas, simulation, circuit publication, and reuse. The missing opportunity to investigate is the release process around those circuits. A reusable component needs more than an NFT number. Its consumer needs to know what each pin means, how its state behaves, which dependencies it uses, and whether a new version changes its behavior. CircuitPack would package a TapeOut circuit with: - Named and ordered input, output, and state pins. - A behavioral specification. - Exact processor, circuit, and chain identities. - Locked dependencies and reproducible builds. - Test results and concrete counterexamples. - Compatibility reports between versions. Consider an instructor publishing a four-bit saturating counter. It should stop at 15. A student submits a smaller replacement that accidentally wraps from 15 to zero. CircuitPack identifies the precise failing transition: prior state 1111, enable asserted, reset clear. It shows the expected state and both implementations’ results. The instructor can reject the change or explicitly publish a different specification. That is more useful than another counter demo: it helps someone depend on the counter. Its native integration would be: Specification and locked dependencies → NAND/LATCH compilation → Local reference comparison → TapeOut processor selection → Component minting and tape-out → Circuit NFT → eval/step comparison → Versioned package and report For stateful packages, the verifier passes each returned state into the next step call. It does not repeatedly test from zero and call that a complete execution trace. Small combinational circuits can receive exhaustive truth-table checks. Small stateful circuits can receive complete bounded transition comparisons. Larger designs need explicitly limited testing; sampled tests must not be sold as mathematical proof. The commercial opportunity is release maintenance: team packages, CI checks, compatibility reports, and reproducibility support. Public circuit evaluation remains public. Owning the NFT does not grant exclusive execution rights. First pilot: one builder team and one instructor, six components, and one deliberately broken upgrade. Ask a second person to reproduce and integrate each package without contacting its author. Reason to stop: people do not reuse components, or a repository plus the existing canvas already solves the problem adequately. This is my strongest first-build candidate because it improves the existing ecosystem without immediately taking custody of customer money. @XLayerOfficial
Good ideas deserve to be heard. Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT. Ends Nov 17. Submit here: bit.ly/4eQxFIH
18
16
42
526
Heisbei retweeted
Introducing SwarmKit, the coordination layer for agent economies on @NEARProtocol Live implementation of SwarmKit below, built at NEAR HACKATHON #NEARHackathon Full docs: swarmkit.pages.dev Swarm market (Demo): swarmkit-coop.pages.dev @ilblackdragon
5
3
18
444
Savings nobody can touch, not even us. Introducing Sevu Most savings apps ask you to trust whoever holds the money. On-chain locks remove that trust, but they usually need gas tokens and approvals that Nimiq Pay users don't have. So I built around that. Sevu is a Nimiq Pay mini app. You lock USDT until a date you pick, and it sits in a public Polygon contract with no owner and no admin. You pick an amount and a date, then sign twice in Nimiq Pay. The relayer pays gas, so your wallet can hold zero POL. Until the date, withdrawals revert for everyone. After it, the full amount goes to the owner and nobody else. You don't need a wallet to check the claims. Open the proof page, and it asks the live contract whether a stranger can pull a lock early and whether any admin functions exist. There will be a reward for the first 20 users who lock USDT in Sevu No limits to how many you can lock Code: github.com/mystiquemide/sevu Live app: sevu.midelabs.xyz Watch the video below to learn how it works @nimiq @NimiqCommunity
Most savings apps hold your money. Sevu can't. Lock USDT until a date you pick, inside Nimiq Pay. It sits in a contract with no owner and no admin. Nobody can move it early, not even us. First real lock went in today on @nimiq Two signatures, zero gas. @NimiqCommunity
7
5
1
22
1,074
Heisbei retweeted
Turning a trading idea into an automated strategy is complicated. Testing it, proving what was created,and making it available for others to follow is even harder. Quorumark brings all of that into one AI-powered marketplace,with verification on @NEARProtocol #NEARHackathon 🧵
5
4
11
389
Heisbei retweeted
For the NEAR HACKATHON, I built Fiador, Members borrow treasury NEAR at once within their standing, a council grant that grows with every on-time repayment When a DAO wants to lend to its members, who decides? Today nobody, because a DAO treasury only pays out, and every grant is a full council vote. Credit unions solved this long ago: members pool money, and what you can borrow grows with your record. Fiador gives a Sputnik DAO the same rules, on NEAR. From my own wallet I asked the treasury for 2 NEAR (loan #11). The desk filed its own Sputnik proposal (#21), voted it, and the DAO paid. I repaid 41 seconds later. Standing went from 7 to 8, and the treasury ended back at 15.4215 NEAR. Earlier, another loan of mine (#7) defaulted under a 120 second term. The council voted to raise it to 600 seconds (proposal 16), and the default stays in the book. What NEAR fits in here : - @SputnikDAO 2.3.1: the treasury. Every loan is a native proposal that the desk files and votes itself, no council vote per loan - The desk's seat can vote on exactly that one proposal and holds transfer rights only - The desk contract has 0 access keys, so it can't be patched, only replaced by a new desk the council seats - A 2-of-3 council sets the rules by proposal: 4 NEAR starting standing, +1 per on-time repay, 10 max, 12 NEAR cap on the book - Three lanes: standing, co-signed (another member pledges the gap), council - A visitor line: faucet newcomers get 0.1 NEAR, repay it, and earn standing - Rust and near-sdk 5.30, Meteor Wallet through Wallet Selector, a static React board with no backend it's live testnet only . The council is three accounts I made with one operator key, and loans 0 to 6 came from that scripted story. Co-signing from the browser board wasn't run with a real wallet. Standing can be pumped with tiny loans; it's in the README. git clone github.com/Dotman-Bei/fiador && cd fiador && npm ci && npm run verify It reads the chain and matches every loan to its Sputnik proposal (24 checks). The board's Desk & proof page runs the same checks in your browser. Try it: dotman-bei.github.io/fiador/… Code: github.com/Dotman-Bei/fiador @NEARProtocol #NEARHackathon @SputnikDAO
12
11
1
32
869
Freelancers in Africa lose 8–9% just getting paid from abroad. And the AI tools they use read their private invoices. So I built PayMe at NEAR HACKATHON: one private payment link, payable from any chain. @NEARProtocol #NEARHackathon 🧵👇
4
3
5
226
Day 1 of my motion design challenge. I’m making motion designs / ads for brands until I land a gig. Starting with @Yoma_World : opportunities are scattered, Yoma puts them in one place, and every one you finish earns a verified stamp on your Yo-ID. Practice piece, not an official ad. I’ll keep getting better each day. Open for motion design and ad work. DMs open.
2
3
6
211
Heisbei retweeted
a full stack developer is just a frontend developer who got curious
191
364
95
3,520
117,626
What if you could buy a tokenized stock without worrying about which version has the best price? Lucas explains how JTX handles this by comparing different versions of the same stock and finding the best route for your trade. Using Nvidia as an example, he shows how RFQ can help users access deeper liquidity with less price movement.
13
10
28
525
Heisbei retweeted
feeling much better now. to everyone who wished me well, thank you. gm, let’s get back to work.
91
3
118
955
Solana's speed keeps improving, and Lucas says JTX is already faster than Coinbase when it comes to executing SOL-USDC trades. Lucas shares how JTX confirmation times have dropped from 500 milliseconds to as low as 100-200 milliseconds. And according to him, this is only the beginning. "This is the slowest it'll ever be."
17
8
34
577
In 2018, Arkansas cut about 18,000 people from Medicaid. Most of them qualified. They lost their coverage to paperwork. On December 31, 2026, a rule like that goes national: 80 hours of work, school or volunteering, or $580 of pay, every month, with proof. So I built Eighty. It does that paperwork from the phone people already use. Send a pay stub photo or a voice note in English or Spanish on Telegram. Eighty reads it and proposes a line. Your month fills in on the web as two rings. Tap "Do my month" and it asks you the one question only you can answer, then gives you a proof packet, cited to the law, ready to send to your state. You can even connect Claude and ask what's left in your month. The agents propose. Only you confirm. Nothing counts until you do. Why it only works on Agent-Native: Eighty has four ways in. Your buttons on the web, the helper on the web, Telegram, and Claude. All four run the same 27 actions, on one database, with the same check of who is asking. Built any other way, that's four separate systems that could disagree about whether someone keeps their health coverage. And the rule that matters most is set on the action itself: the agents propose, only you confirm. No agent, in the app, in Telegram or in Claude, is ever given the confirm button. Built on Agent-Native for the Builder.io Agent-Native Hackathon. Try it, no sign-in needed: tryeighty.space Telegram: @TryEightybot Code: github.com/Jennycruzy/eighty
8
4
1
28
4,465
Heisbei retweeted
𝐏𝐀𝐕𝐈𝐋𝐈𝐎𝐍 is a floor planner for events where event organizers and Ai agents collaborate to design, optimize and manage venue layout in real time. It allows users to create scaled floor plans, arrange seating , stages and equioment and explore layouts in 2D or 3D. It’s intelligent layout engine automatically checks spatial constraints , seating capacity, safety requirements and costs ensuring every design is pratical and ready for execution. Rather than making changes without permission, the ai proposes improvements that users can review, compare and approve, keeping humans in control throughout the planning process. 𝐇𝐎𝐖 𝐈𝐓 𝐔𝐒𝐄𝐒 𝐀𝐆𝐄𝐍𝐓-𝐍𝐀𝐓𝐈𝐕𝐄 - One action layer: the canvas and the agent call the same defineAction() contracts (move-objects, add-objects, propose-layout, export-setup-pack and others). There is no agent-only path. - Application state: navigation and the current selection are synced, and view-screen returns them verified, so "move this closer to the stage" means the chair you selected. - A human gate in the contract: apply-proposal and restore-version are UI-only actions, hidden from the agent's tools and MCP. The agent proposes; a person applies. - Every write is versioned and audited in PostgreSQL through the framework's database conventions. Manual editing works with no model key. - Each visitor gets an isolated guest sandbox with rate limits, so the live demo needs no sign-up. Pavilion : pavilion-nine.vercel.app GitHub Repo: github.com/Enoch208/pavilion 𝑯𝒆𝒓𝒆 𝒊𝒔 𝒂 2 𝒎𝒊𝒏𝒖𝒕𝒆 𝒗𝒊𝒅𝒆𝒐 𝒘𝒂𝒍𝒌𝒕𝒉𝒓𝒐𝒖𝒈𝒉 𝒐𝒇 𝒉𝒐𝒘 𝒕𝒉𝒆 𝒑𝒓𝒐𝒅𝒖𝒄𝒕 𝒘𝒐𝒓𝒌𝒔 @Steve8708 @builderio @tempoimmaterial
27
17
55
2,176
Need your help Please vote by liking circle sats 🙏 dakar-bitcoin-hack-2026.devp…
Building Circle sats Àjò on bitcoin for the Dakar hack
23
12
6
45
1,991