Hi all — I’m an independent builder, and I’d love feedback on something I made on the Sui stack, plus some guidance on next steps.
Elur is a native macOS app for governed file sharing. You encrypt a file on your own device, send it through any channel (email, WhatsApp, (THE SUI TEAM WILL NEVER ASK YOU TO LEAVE THIS SITE)), and can revoke, expire, or limit access AFTER you’ve sent it — even on copies already delivered. The goal is consumer-grade UX: a non-crypto person signs in with Google, encrypts a file, and never knows a blockchain was involved.
How it uses the stack:
- Seal — the file’s content key is sealed to an on-chain AccessPolicy (Move) via threshold encryption. seal_approve gates decryption on the policy’s state (expiry, max-opens, revoked). Revoking flips the policy on-chain, so future seal_approve checks fail and the file stops decrypting anywhere.
- zkLogin — sign in with Google, no seed phrase or wallet.
- Enoki — sponsored gas, so the user never touches gas.
Recipients open files with no account at all.
Status: working on Sui testnet today — full loop verified (encrypt → mint policy → open → revoke → sealed).
Two things I’d genuinely value:
- Feedback on the Seal usage / access-policy pattern above — is this a sound way to do it?
- With the RFP list currently empty, what’s the right path or process to get something like this in front of the grants / ecosystem team? I’m trying to get it audited and to launch, and I can’t find the front door.
Happy to share a short demo and a one-pager.
Best regards,
Andrés Córdoba