Now, who wants to give me feedback for the project?
Backup solutions usually suck, they make you KYC and provide an xpub, so they see all of your balances and transactions.
Us plebs aim to fix that, reputational based trust, geographic distribution, no kyc, no multisig xpub shared.
The trust is between the client and the backup key provider, where it should be.
KYC für Backups? Lacher! Das ist der wahre Raub, deine Freiheit in tausch für unnötigen Schwachsinn. #Seed-E klingt spannend, klingt nach echter Bitcoin-Funktionalität. Gut, dass ihr an die eigene Sicherheit denkt, während die Zentralbanken euer Geld unterdrücken!
nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz3rhwvaz7tmed3c8qarfxaj8s6mrw96kvef5dve8wdrsvve8vvehwamxx7rnwejnw6n0d3axu6t3w93kg7tfwechqutvv5ekc6ty9ehku6t0dchs8t6269 here is the start of a project, a humble weekend vibe code. What say ye? Worth pursuing further?
New update for Seed-E
https://github.com/kiwihodl/Seed-E/tree/signature-requests
feat: implement signature request feature with PSBT validation and payment flow
- Add complete signature request workflow with payment-first approach
- Implement robust PSBT validation using byte-by-byte parsing (BIP 174) to ensure there are no signatures
- Add master fingerprint and derivation path fields to service model and provider forms
- Create comprehensive API endpoints for signature request lifecycle
- Add client dashboard with signature request management
- Implement provider dashboard for handling signature requests
- Add signature request payment modal with Lightning invoice integration
- Include PSBT upload with drag-and-drop and validation
- new testing and cleanup scripts
Need to test this on the providers side. Ensure the new values (master fingerprint, derivation path etc) are encrypted at rest. I am thinking the PSBT should be encrypted at rest too and considering that each client and provider should have a set private (their master key) and public key, so we can do a diffie helman encryption so only they can decrypt on each side (optional to do it locally outside of the platform).
Huge shoutout to nostr:nprofile1qqs9p6pwfs8fuvynkmj2fxrd8gqjfnp37z296jp6elfqxrpqzt8v0fspypmhxue69uhhyetvv9ujuargv4hhyctwvajhq6tvd3shqupwvdhk6qguwaehxw309ahx7um5wgkhyetvv9ujuamvweejuumsv93k2nczqsj for purchasing the domain:
seed-e.org
And for providing free hosting at their data center.
Should be an operational alpha by end of week.
I will fork @SparrowWallet next week and insert the marketplace as an option when creating a multisig, hitting the APIs, so I can give a working example of how it can be implemented into wallets.
Looking for some testers and feedback.
www.seed-e.org
TLDR, a marketplace for uncle Jims
It's not hard to self custody, people just don't want to share the burden of being solely responsible. If we don't fix this, they will end up with KYC & AML custodians which completely defeats the purpose and makes Bitcoin a social credit system, just with a finite amount (at best).
What I Accomplished Today:
🔐 Phase 1.5 Encryption Completed:
✅ AES-256-GCM encryption for XPUBs, PSBTs, and payment hashes
✅ Context-specific key derivation for different data types
✅ IV and auth tags for tamper protection
✅ 6 encrypted database fields confirmed working
⚡ Lightning Architecture Cleanup:
✅ Removed unused LND/Voltage dependencies, replaced with LNURL
✅ Cleaned up environment variables
📚 Documentation Updates:
✅ README roadmap updated to show Phase 1.5 completed
✅ Removed Lightning node requirements
✅ Updated encryption status in project documentation
Ready for Testing!
The app is now running with:
✅ Proper encryption for sensitive data
✅ Decentralized Lightning (no node required, just a valid LNURL address e.g highlyregarded@getalby.com)
✅ Fixed signature requests
✅ Cleaned and updated architecture without unused dependencies
Huge shout out to nostr:nprofile1qqs9p6pwfs8fuvynkmj2fxrd8gqjfnp37z296jp6elfqxrpqzt8v0fspp4mhxue69uhkummn9ekx7mqpz3mhxw309ucnqvpw8qmzuvfwxvargwp58qmpvcqg for believing in me and his support.
For those wanting to test, I only have SeedSigner set up to export the multisig xpubs (choose BlueWallet when exporting from SS). Also, ensure you have a valid LNURL (e.g highlyregarded@getalby.com )
You can now list keys for sale, buy them as a client, request the provider for a signature, the provider then has the minimum days (currently 7, open to push back) cooling period before signing (first signature only) and sending back to the client.
Ideally, this would be a blinded Xpub (BIP32) using chain code delegation, scalar tweaks and blinded schnoor signatures, for ultimate privacy… but there is a lot of hurdles to jump through before that is widely accepted and possible. In the meantime, a simple BIP32 Xpub and backup will be the first service. Yet to configure it that way though, just had to get initial MVP out there for feedback before any polishing and restructuring.
