Загрузка видео...

Не удалось загрузить видео

На главную

NO SEED PHRASE ❌ Your wallet shouldn’t begin with 12 words that can be stolen. In this video, I’m creating a MarvelX wallet using a PQC Vault File — no seed phrase, no screenshots, no clipboard leaks. The PQC Vault is a 320KB file made of algorithmic combinations based...

95,104 просмотров • 7 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

We are excited to announce the launch of QShield Terminal, the world's first Quantum-Secured Privacy Terminal for Ethereum. QShield brings full financial privacy to Ethereum without the need for mixers, tumblers, or any third-party tools. Everything is handled directly through the QShield interface using zero-knowledge proofs on RAILGUN Protocol. What QShield Terminal offers today: • Shield any ERC-20 token from your public wallet into a fully private balance • Send and receive tokens with zero on-chain trace • Create multiple independent shielded wallets • Transfer between your own shielded wallets with no connection between them on-chain • Switch between public wallets to fund your shielded balance from any wallet you own • Support for ETH, USDC, USDT, DAI, WBTC and 290+ ERC-20 tokens • Quantum entropy wallet generation using real quantum randomness • 100% web-based, no downloads, no browser extensions No mixer. No tumbler. No compromises. Just real privacy through cryptography, accessible to everyone directly from the browser. This is the first product of its kind. No other privacy solution combines multi-shielded wallets, inter-wallet transfers, quantum entropy, and a full guided interface in one place. You can try it now: We are working on additional features including private token swaps directly from your shielded balance, and we will keep expanding the protocol with new capabilities over the coming period. We keep building. RAILGUN - Private Ethereum DeFi

Qubit

26,120 просмотров • 5 месяцев назад

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

CoinBets🔍

20,973 просмотров • 5 месяцев назад

DON'T LET YOUR BITCOIN DIE WITH YOU 💀 ⚰️ Yea look, nobody likes to admit it but we all have to die one day. As I've been talking to people about their self custody lately - both Casa members and not - I hear the same thing over and over. "What happens if I die?" Many people feel pretty good about their bitcoin security for themselves. But their family members often have no idea how to use this stuff. Hardware wallet? Seed phrase stamped on metal? Shamir's secret sharing backups using SD cards, a passphrase, and a treasure hunt through the backyard with a shovel? 😵 We're solving that problem for all Casa members, starting today with Casa Inheritance. A key design principle we kept while building this was to make it as simple as possible for Recipients (your family members that will receive your bitcoin if you pass), while maintaining Casa-level security. An estate transfer is already a stressful time for family, and it can become even more stressful if you add in a crazy treasure hunt to access a fortune in bitcoin. For our basic 3 key vaults, we wanted it to be as easy as using the app. No metal plates, no need to use a hardware wallet, no magic passwords you have to keep track of or else risk messing up the asset transfer. Simplicity is security. So how does it work, in detail? A Vault Owner (Casa member) designates a Recipient (their family or friend) in the Casa app. The Recipient receives an invite to create a free Casa account. The Recipient scans a QR code provided by the Vault Owner, which contains an encrypted version of the owner's mobile key. This encrypted key is only able to be imported by the Recipient's Casa account, and the Recipient can't initially use it or see the vault balance. If the Vault Owner passes away, the Recipient can request access to the vault in their Casa app. This starts a 6 month timer, and sends a ton of notifications every month to the owner. If the owner is still alive, they can reject the request in app. If they are not, the timer will run out. When it does, the Recipient will be able to use the shared mobile key and the request a signature from the Casa Recovery Key for the shared vault. This gives them 2 out of 3 signatures, enough to access the assets. For 5 key vault users, one hardware key is shared with the Recipient. This small increase in friction for Recipients is often worth it for the increased security and resilience of a 5 key vault for larger holdings. To summarize now that you have the details: 1. Share keys and vault access during setup 2. 6 month timelock to ensure no malicious theft 3. Use shared keys and Casa key to access assets Full setup takes less than 5 minutes. Inheritance is one of the biggest problems in self custody today. If you've hodled through years of painful bear markets, you owe it to yourself and your family to not let the reward for that patience go to zero because you didn't have a plan - and we're here to make that easy. Check out the video to see how easy it really is. Like I said earlier this week - Casa is going after major problems in self-custody this year. Check this one off the list ✅. Next one coming sooner than you think 🔥.

Nick Neuman

125,739 просмотров • 2 лет назад