kloak

novel fungibility layer built on kaspa, the world's fastest cryptocurrency. take control of your money. in development

$KAS #Kaspa

[kloak @kloakprotocol]

@ziwenxu_ Hey man, switch to DeepSeek V4 pro. It's 10x cheaper and still fantastic.

[kloak @kloakprotocol]

i don't think we understand how quickly #Kaspa covenants hard fork will change the world.

kloak stealth addresses in the pipeline...

$KAS

[kloak @kloakprotocol]

@BTCForevercast @KaspaSilver @thekaspaonion @kurtwuckertjr hey (soon)

[kloak @kloakprotocol]

@HocusLocusT @JTMcGibbon the code will be open source absolutely, and if you want to do it yourself you can buy an esp32 microcontroller and flash it for dirt cheap.

you're thinking too much like a crypto nerd, not on the masses' wavelength.

plug and play is necessary for widespread usage

[kloak @kloakprotocol]

@KaspaHub amen

[kloak @kloakprotocol]

@JimWallberg @0xalank @mechanikalk @neo_zambas in what sense?

it is confirmed and spendable within 1 second yes

[kloak @kloakprotocol]

@JimWallberg @0xalank @mechanikalk @neo_zambas 50,000 bytes is irrelevant when internet speeds in the modern day are measured in giB/s

[kloak @kloakprotocol]

@JimWallberg @0xalank @mechanikalk @neo_zambas me pressing 'send' in my wallet and having the money appear with finality in another persons's wallet within 1 second is something that neither bitcoin nor quai accomplishes

[kloak @kloakprotocol]

@JimWallberg @0xalank @mechanikalk @neo_zambas how is it a 'waste of bandwidth'?
whos bandwidth? It is what allows kaspa to power the financial activities of billions without sacrificing security or decentralization

[kloak @kloakprotocol]

@0xalank @JimWallberg @mechanikalk @neo_zambas wow, 1700 tps on a testnet! pretty impressive

the point was not adoption. the point was demonstrating the robustness of the dag in the real world

[kloak @kloakprotocol]

@0xalank @JimWallberg @mechanikalk @neo_zambas cool. kaspa is theoretically capable of over a billion transactions a day, limited only by internet latency, really.

we don't need smart contracts on chain because it is unnecessary. zk is totally sufficient for money programmability.

[kloak @kloakprotocol]

@0xalank @JimWallberg @mechanikalk @neo_zambas tx per block = wider pipe
bps = higher pressure

kas has done 158 million transactions in a day without any shutdowns or issues.

we can talk when quai matches that

[kloak @kloakprotocol]

@JimWallberg @0xalank @mechanikalk @neo_zambas lowering the latency between blocks reduces the time it takes for your broadcasted transaction to be confirmed in a block

[kloak @kloakprotocol]

@0xalank @mechanikalk @neo_zambas faster block times reduce the delay between the propagation of a transaction and its inclusion in a block. the only limit is network latency. more bps = sooner hashrate is applied to your tx

[kloak @kloakprotocol]

@0xalank @mechanikalk @neo_zambas all other variables staying the same, from broadcast to confirmation and finality, a kaspa transaction is 10x faster now with crescendo than it was at 1 bps. I am emphasizing real-world functionality, not theory.

[kloak @kloakprotocol]

@0xalank @mechanikalk @neo_zambas yes but that hashrate culminates in a block being discovered. think bitcoin, it may have a hashrate orders of magnitudes higher than kaspa, but practical network confirmation for a broadcasted transaction is far lower than kaspa. dagknight is the goal for kaspa.

[kloak @kloakprotocol]

@0xalank @mechanikalk @neo_zambas because confirmation probability is based on blocks, not on transactions. kaspa transactions are statistically "guaranteed" after 10 blocks (yes, somewhat arbitrary). 1 bps = 10 second confirmation, 10 bps = 1 second confirmation, and so on

[kloak @kloakprotocol]

@0xalank @mechanikalk @neo_zambas and if the network demand is fully captured at 3bps, then yes, increases in the amount of blocks per second does improve throughput and finalization times...