
Torrezno 𐤊
40.9K posts

Torrezno 𐤊
@Torrezno420
Evolution is unstoppable


🚀 Hey everyone, what do you think? I was honestly sick of passwords — constantly creating new accounts, forgetting them, resetting them… Eventually I’d had enough and thought: There has to be a much better way! So I built this: A source-available Authentication Gateway for KBeam & Kaspa. Passwordless login for any website or protected area using QR codes and wallet signatures. Similar in spirit to SIWE/Web3 wallet logins, but built natively for the Kaspa ecosystem. How it works: - The website creates a one-time login request - You approve it with KBeam (version 985 or higher) - The gateway verifies the wallet signature - The website creates its own secure session Big advantages: - No passwords transmitted or stored - KBeam never sees your session cookie - Fully self-hosted and under your full control - Zero tracking, zero personal data - Completely transparent and publicly auditable - Security: KBeam wallet signature ~128-bit vs normal password ~40-bit → approx. 3 × 10²⁶ times harder to crack. No comparison. 🔥 Quick test: - Click the link - If KBeam is installed: open normally in browser and confirm with button on same device - Or scan the QR code (iPhone camera, KBeam Home or in chat) - works on same or different device 👉 kbeam.app/auth-gateway-t… (Everyone is welcome to test 😉) The gateway is self-hostable and can be further developed and integrated into your apps. Future vision: Building a “Trusted Customer Layer” with optional direct chat, support, updates and more — always under your full control. I’m really proud and hyped about this! 🔥 What do you guys think? Would you integrate something like this? Let me know! ⚡ #KBeam #Kaspa







🚀 Hey everyone, what do you think? I was honestly sick of passwords — constantly creating new accounts, forgetting them, resetting them… Eventually I’d had enough and thought: There has to be a much better way! So I built this: A source-available Authentication Gateway for KBeam & Kaspa. Passwordless login for any website or protected area using QR codes and wallet signatures. Similar in spirit to SIWE/Web3 wallet logins, but built natively for the Kaspa ecosystem. How it works: - The website creates a one-time login request - You approve it with KBeam (version 985 or higher) - The gateway verifies the wallet signature - The website creates its own secure session Big advantages: - No passwords transmitted or stored - KBeam never sees your session cookie - Fully self-hosted and under your full control - Zero tracking, zero personal data - Completely transparent and publicly auditable - Security: KBeam wallet signature ~128-bit vs normal password ~40-bit → approx. 3 × 10²⁶ times harder to crack. No comparison. 🔥 Quick test: - Click the link - If KBeam is installed: open normally in browser and confirm with button on same device - Or scan the QR code (iPhone camera, KBeam Home or in chat) - works on same or different device 👉 kbeam.app/auth-gateway-t… (Everyone is welcome to test 😉) The gateway is self-hostable and can be further developed and integrated into your apps. Future vision: Building a “Trusted Customer Layer” with optional direct chat, support, updates and more — always under your full control. I’m really proud and hyped about this! 🔥 What do you guys think? Would you integrate something like this? Let me know! ⚡ #KBeam #Kaspa




🚀 Help us get Revolut’s attention! We want to see Kaspa (KAS) listed on Revolut — one of the fastest and most innovative PoW cryptocurrencies out there. 👉 Like, repost, and share this flyer so it reaches @RevolutApp! The stronger the community, the louder the message. Let’s make it happen. #ListKaspa #Kaspa #Crypto #Revolut


Normal transactions are dominated by sig cost (1000 compute gram per sig, where 500k is the compute mass block limit -> max 500 sigs per block). Compute mass also counts byte size (1 gram per byte), so 500 sigs are unrealistic, hence the known ~300 txs per block number. It assumes 300 1:2 txs (1 in, 2 outs) with minimal size. Increasing the block *byte-size* limit (aka transient mass) from 125kb to 250kb means that you are still constrained with 300 typical txs but they can carry more data (eg in their payload) a stark proof on the other hand, costs 250 sigops + ~225kb in size. so compute mass is at least 250*1000 + 225kb = 475kg ~< 500kg compute mass limit and raw size is, as said, 225kb so it’s still bellow the transient mass limit


Toccata reached feature freeze That means $KAS' hard fork is basically ready to go and bring ZK proofs and programmable UTXOs to the chain (among other things) No more tweaking with the rules, this will go live in a month from now ⌛











