kloak

99 posts

kloak banner
kloak

kloak

@kloakprotocol

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

the multiverse Katılım Mayıs 2022
89 Takip Edilen532 Takipçiler
kloak
kloak@kloakprotocol·
@SaluizaSasha @vessprotocol No, I did what anyone would do while working on a project which is test the waters for interest, let the community know about direction and garner potential interest. I didn't start with the intention of starting a new network. But it has to be done to accomplish what I want
English
0
0
1
21
Mr. 𐤊asparov
Mr. 𐤊asparov@SaluizaSasha·
@kloakprotocol @vessprotocol Did you first make yourself loved by the kaspa community and then download it by promoting your own protocol? Damn man you're ridiculous...What kind of excuses then... 🤡⏰️😂🙌🏾
English
1
0
1
77
kloak
kloak@kloakprotocol·
4/4 I eventually realized I was trying to fit a triangle into a square hole. the network that fulfills the satoshi ethos hadn't been built, like i thought it had in kaspa:native so i started building @vessprotocol a new network, PQ, private, scalable natively
English
13
1
10
2.4K
kloak
kloak@kloakprotocol·
@NikolaGalilei I never said it was impossible. I said Kaspa's architecture forces compromises I didn't want to make. I would say native quantum resistance requires statelessness. I hope someone else builds PQ on kas. I won't be balancing dominoes on a pinhead personally
English
1
0
0
87
KaspaFacts
KaspaFacts@NikolaGalilei·
@kloakprotocol 1/4 - Bullshit (I literally wrote a rust port of a quantum resistant set commitment as well as described how to use it in Kaspa, it is NOT computationally prohibitive) 2/4 - more Bullshit 3/4 - Bullshit (see PoChM/Part Seq Comm KIP6/KIP21) 4/4 - SMH
English
4
3
33
570
kloak
kloak@kloakprotocol·
3/4 my assumptions about $KAS covenants during kloak development were too optimistic. I came to realize that the pruned, data-hostile chain forced betrayal of full decentralization, and usage of off-chain data storage, APIs, and compromises I never intended to have to make
English
3
0
10
6.4K
kloak
kloak@kloakprotocol·
2/4 like many other crypto networks, kaspa:native has an arguably insurmountable battle ahead of it to migrate to PQC. cryptocurrency must fundamentally change to support the scaling required for actual adoption without compromises. bigger or faster blocks will not cut it.
English
1
1
9
953
kloak
kloak@kloakprotocol·
dear #Kaspa community: in my development of kloak on kaspa:native , I unfortunately came across limitations that I believe cannot be overcome. kaspa, as innovative as it is, suffers from 100% architectural reliance on quantum-vulnerable cryptography. will explain more: 1/4
English
6
2
22
7.8K
kloak
kloak@kloakprotocol·
@ziwenxu_ Hey man, switch to DeepSeek V4 pro. It's 10x cheaper and still fantastic.
English
0
0
0
176
kloak
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
English
4
14
81
2.2K
Kurt Wuckert Jr
Kurt Wuckert Jr@kurtwuckertjr·
Every single thesis that the small blockers have said bitcoin is for has failed. BTC isn’t a reliable settlement layer for L2, it isn’t a reliable store of value under pressure, and it isn’t even a decent inflation hedge. Even has a base fiat speculation tool, you’d have been better off in all kinds of stocks and precious metals. Meanwhile, big blockers have been proven right about scalability, Turing completeness and lots of other claims about bitcoin’s fundamental properties. When will people completely reject the people who hijacked bitcoin?
English
39
34
156
10.5K
kloak
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
English
1
0
4
108
Ricardo Sanchez
Ricardo Sanchez@HocusLocusT·
@kloakprotocol Ideally people don’t have to ‘buy’ some hardware you guys are selling. It should be accessible + open source so it can be integrated into @JTMcGibbon All-In-One project.
English
1
0
1
89
Classic
Classic@Classicxbt·
Kaspians are technology maxis. We keep our eyes wide open and our logic sharp, investing in the future - not the feeling.
English
1
3
56
1.1K
Neo 𐤊
Neo 𐤊@neo_zambas·
It's crazy that's $KAS is PoW, does 10 blocks per second, and most of the world doesn't know yet.
English
28
43
289
8.4K
kloak
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
English
1
0
0
31
kloak
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
English
1
0
0
31
Jim Wallberg.quai
Jim Wallberg.quai@JimWallberg·
@kloakprotocol @0xalank @mechanikalk @neo_zambas To me a step size of 600 ms is the same as a step size of 100 ms. Like a 100 ms step size wouldn't give that much more depth of partial finality over a 600 ms step size. It's not necessary at all. And wouldn't be a selling point of a higher bps that wastes bandwidth.
English
2
0
0
38
alan ⚡💵
alan ⚡💵@0xalank·
158 million botted transactions a day isn’t going to do anything for adoption On top of that, Quai tested 1,700 TPS+ sustained during the Iron Age and Golden Age testnets all pre-launch We validated our scaling mechanism before go live hence there is no need to do a test in production for shits and giggles
English
2
0
1
56
kloak
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.
English
0
0
1
44
kloak
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
English
2
0
1
115
Jim Wallberg.quai
Jim Wallberg.quai@JimWallberg·
@kloakprotocol @0xalank @mechanikalk @neo_zambas First let's target the finalization, how does increased bps decrease time to finality? Are you saying that when scaling from for example 1 bps to 10 bps to 100 bps, each block maintains the same level of finality?
English
2
0
1
109
kloak
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
English
0
0
0
9
alan ⚡💵
alan ⚡💵@0xalank·
Finality is not based on number of blocks, it’s based on aggregate work or hashrate securing the network. If there are 10 bps or 100 bps there is no difference if the hashrate does not change (which it does not). Confirmations are a measure of finality within a period but the number of confirmations required can change in a proof of work system depending on 1) value sent 2) current hashrate
alan ⚡💵 tweet media
English
3
0
0
28