Heisbei @Heisbei02

RWA tokenization is scaling, and @iEx_ec own RWA documentation names the reason institutions hesitate: on a public chain, every balance and every transfer is a matter of public record. That framing stops at issuance. Institutions don't trade size on-chain. Public order books leak your limit price, your counterparty, your flow. Zerk is a dark pool for tokenized real-world assets. Encrypted orders. Matching inside a TEE. Atomic settlement on unmodified Seaport. Built on @iEx_ec Nox ->How it works: Order terms encrypt client-side. The chain stores opaque handles, never values. A blind keeper pairs order IDs without the ability to read them. The TEE decides whether they cross. Only the executed fill is printed. Both limit prices stay secret. ->The privacy claim isn't an assertion. The test suite pulls raw calldata and proves neither limit price appears in it. Live on Sepolia, settling through canonical Seaport 1.6. Live link: zerk-flax.vercel.app Repo: github.com/Dotman-Bei/zerk Built for #WTFHackathon with @iEx_ec

20 4 38 373 0

View Details

Heisbei @Heisbei02

23 hours ago

@kunmiii__ @GenLayer Thank you estar

0 0 1 13 0

View Details

Heisbei @Heisbei02

2 days ago

I just shipped Driftt on @GenLayer Driftt is a cross-game asset layer where AI validators reach consensus on what your item is worth in someone else's game. Cross-game items are fundamentally broken. - Items are trapped in one game forever. - "Interoperable NFTs" only work between near-identical games. - They all rely on one hardcoded stat schema, {attack: 50} means nothing to a space shooter. - The moment two games genuinely differ, the schema breaks and the item breaks with it. - And no studio will let a rival's server decide what a foreign item is worth inside their economy. Driftt replaces shared stat schemas with GenLayer's AI validator consensus. Items never store stats. They store meaning, a plain-English description of what the item is, with no numbers and no stat names. How it works: -> Games register by describing their ruleset in plain English. That string is the integration, no SDK, no shared schema, no standards committee. -> Builders play. Killing a boss produces a gameplay event, not a mint button: "defeated the Ashfall Dragon without taking a single hit, finished on 62 of 100 health." -> An Intelligent Contract forges the reward: an LLM designs a balanced item from what the player actually did, and validators independently re-run it and must agree the power tier is justified before anything is stored. -> The player translates the item into another game. The contract reads the item's meaning plus the target game's ruleset and reasons about the fair equivalent. A fire greatsword becomes a plasma lance. -> Validators reach consensus using GenLayer's Equivalence Principle: outputs do not need to be identical, only equivalent, same archetype, same theme, power that doesn't inflate. -> A deterministic clamp after consensus holds power within ±5 of the origin tier. Even a fully compromised validator set cannot mint a god-weapon into someone else's economy. -> Items evolve through use, under a ceiling that shrinks every time they grow, so they can't be farmed into god-tier. Why GenLayer: There is no deterministic function that maps {ATK, DEF, ELEMENT, DURABILITY} into {DAMAGE, SHIELD, FIRE_RATE, ENERGY_TYPE, OVERHEAT_RISK}. The mapping is a judgement about meaning, not arithmetic. You can't do that reasoning on a deterministic chain. You can't do the trust off-chain. No other blockchain natively embeds LLM execution and subjective consensus. Traditional chains push this to external oracles. GenLayer makes it part of consensus itself. Running live: forge, translate and evolve all settle on-chain through the app, strictly. Also proven on the public Bradbury testnet at 6-of-6 validator consensus. Live link: driftt-pi.vercel.app GitHub repo: github.com/Dotman-Bei/dri…