david

[david @davidho73046186]

@zerodmsion 币安要是能把kaspa合约去掉就完美了，不上币，但是kaspa的钱不少赚。

[david @davidho73046186]

@binance Only $kas worth that.

[david @davidho73046186]

@BingXListing @BLOCX_TECH Real Gem $blocx

[david @davidho73046186]

I'm going to #TechCrunchDisrupt2025! Join me and 10k tech leaders in SF! https://t.co/NKuJdNdtPr

[david @davidho73046186]

Excited for the $BLOCX TaskOn campaign! Join @BLOCX_TECH to earn rewards by completing fun Web3 tasks. Don’t miss out—start now! 👉 https://t.co/Fd3OTRPNUE #BLOCX #Web3 #CryptoRewards

[BLOCX. (Official) @BLOCX_TECH]

🚀 GRIDBOX is Now Live

We’re proud to roll out the latest version of GRIDBOX — the most intuitive decentralized GPU marketplace by BLOCX.

Rent. Host. Earn.
Put your hardware to work and start earning today.

And this is just the beginning — more features, templates, and an even more user-friendly experience are on the way.

The marketplace is now open to the world. 🌍

[BLOCX. (Official) @BLOCX_TECH]

⏳ 2 days until launch.

With GRIDBOX, you don’t just rent power — you own your place in the network.

From AI to gaming to mining, the future of compute is almost here. 🔥

[david @davidho73046186]

@Lovrincrypto $kas, as always.

[david @davidho73046186]

区块链未来资金会慢慢流向一些实际应用，还是有些新手和散户会去追一些炒作项目，在这里提醒一下，当你知道项目的时候，已经是后期了，这种项目击鼓传花传不了很久的，项目方这两年也缺钱，没耐心陪你玩太久。把资金投到一些有真正应用的项目上慢慢等着吧。

[david @davidho73046186]

@zerodmsion 多做运动，活得久点，更长时间享受哈哈

[david @davidho73046186]

@zerodmsion 以太坊就不停做空就行，最后肯定大赚

[david @davidho73046186]

@krakenfx @CryptoChrys17 Hi, Please open $Kas stake for earning , I will transfer all my kas to kraken.

[david @davidho73046186]

$kas持币者请把kas从mexc和gate转到kraken, 原因很多，主要是kraken是合规一线交易所，还提供了kas/usd的直接交易对，转换成usd以后可以通过wise直接出金到支付宝/微信，合规提供的交易池，避免了黑金被叔叔借以种种理由给你封账户。还有gate最近那一针多空都吃，你们感觉未来靠谱吗？

[david @davidho73046186]

@ourcryptotalk $Kas is far ahead.

[david @davidho73046186]

@abei1210 单凭免费上kas来看，kraken就是一个有格局的所，比其他的不给钱不让上，或者只上自己投资或者持有大部分代币的自有项目的国人所强太多了。

[david @davidho73046186]

@krakenpro It’s obvious that kraken is much more smarter than other tier-1 exchanges.

[david @davidho73046186]

@zerodmsion kraken是第一个上线kas的tier 1,估计其他tier 1都眼馋了，因为kas持有者又有钱，又有信仰，数量还多，kraken这次赚大发了，其他交易所可能也着急了。

[david @davidho73046186]

kaspa的智能合约将颠覆之前的技术！下面是文章深度解读：https://t.co/4rJbZJZ1VM

[Shai (Deshe) Wyborski @DesheShai]

Hi $kas. @hashdag just dropped a very important post about the L1/L2 zk SC design for $kas he has been fervently working on with @MichaelSuttonIL, @dimdumon, @VolokhIlia, and others:
https://t.co/fAJJc1zeNd

This post, for me, is the ultimate answer to "what is Kaspa good for?".

Not unexpectedly, this is a post written for peers, whereby it is densely written and relies on considerable jargon (sometimes internal jargon whose meaning is left for the reader to understand from context). Here is my best attempt to distill the key point for less technical readers.

The core notion of the entire discussion is atomic composability. In the context of computation, the term "atomic" usually means that an action is indivisible, it is either carried out in its entirety or not at all. The textbook example is transferring money from your bank account -- when you do, two things must happen: your balance is reduced, and the recipient balance is increased. However, we cannot tolerate a situation where only one of these things happened. It is the bank's responsibility to make sure that either all related balances are appropriately updated, or the action doesn't go through at all.

An example that is more on point is cross-chain transactions. Say I want to pay someone some USDT to buy some Kaspa. How can we make sure that either both of us or none of us transfer the money? The current solutions such as CEXes or escrow services are far from perfect, and have been exploited many times by schemers and hackers.

Is it possible to "atomize" this process? To somehow guarantee, cryptographically, that either none or both of the transfers take place? This problem is called "atomic transfers", it is the simplest problem in discussion, and it is already quite difficult. In particular, it requires two disparate chains to depend on one another. But it is more complicated than that: one can think that having an SC on chain A that only transfers money once its counterpart was transferred on chain B could be a solution, but they would be wrong. Say that for some reason the transaction on chain A reverts, would chain B be programmed to return the money? What if it was already spent? Say that the code on chain B had a bug or a malicious backdoor, chain A never checks that chain B transferred the money correctly. If you have both chains observing each other, who is the one to make the first move? You see where this is going.

Atomizing transactions is just one example. Some operation are atomic by nature, you can't "partially" process a simple transaction from one UTXO to another. Either it is processed or it is not. A holy grail of having interoperable SC L2s is the ability to take two atomic operation and transform them into a new atomic operation that does both. This is what we call "atomic composability".

Obtaining atomic composability within a single "logic zone" (a term used in the post, roughly meaning some domain of assets all controlled by the same state) is not trivial, but possible. The real challenge is enabling actions that affect several logic zones in an atomic way. Cross chain transfers are a prototypical example. Currently, the way to wrap one coin in another network is to have a bridge operator that holds on to the wrapped coins and issues tokens on the destination chain. We have to trust the operator to hold on to enough liquidity to allow all users to cash out their tokens if they want to. Such services are hard to establish, centralized and costly.
Imagine if instead we could have just atomized locking coins on one chain while issuing tokens over the other, where the lock can only be opened by burning the tokens. If we had an infrastructure that allows us to atomically compose operations that affect both logic zones (the original chain and the chain holding the wrapped tokens), we could do that!

The trade-off in SC design pretty much boils down to these two extremes:
- logic zones that do not sequence on-chain cannot be verified from the chain, and hence cannot provide atomic composability across logic zones. They thus have to resort to async composability. There are several ways to achieve this type of composability, but the bottom line is that it requires some protocol where each logic zone interacts with the other logic zone and waits for a response. This means that, while working within the logic zone might be very fast, multi-logic transactions become as slow as the settlement times of the involved chains.
- Using on-chain sequencing to achieve composability allows the verifiers of the base layer to make sure all conditions properly holds on both sides before processing the operation, providing the sought-after atomicity. The deterrent to this approach is that on-chain sequencing means that progressing the state of the logic zone is subject to the latency and costs of using the base layer.

This trade-off is a difficult one. Since L1s are limited in their throughput and latency (and since support for on-chain sequencing has to be developed on the L1) we see mostly the former type. However, this is where Kaspa comes in. Given the superior throughput and latency it provides, it could provide us with a best-of-both-worlds solution: providing the luxury of multi-logic atomic composition with internet-fast latency and reasonable operational costs. Or as described in the post: "I think that the construction I’m proposing here extracts the best of all architectures: Bitcoin, Ethereum (rollup-centric roadmap), Solana—an internet-speed version of Nakamoto base layer (verification-oriented), a zk-based computation layer, and a Solana-like unified defragmented state."

(N.B. One point absent from the post that's worth mentioning is that existing chains do not have to migrate to Kaspa to use this feature. There are several possible hybrid designs, such as using the same verification they use today, but adding a component sequencing over Kaspa for the sake of atomic transactions. This is essentially what Yoni meant when he talked about using Kaspa as "a sequencing layer for Ethereum" and it is, in my opinion, a fantastic use case.)

[david @davidho73046186]

@Dodo13080274 跟我感觉一样，我前天就都提走了，关键现在也没个地方能放。kasware也不敢放

[david @davidho73046186]

web3项目都是去中心化的吗？
不见得，很多项目在IPO之前就把所有币发行并且给了投资机构，团队等，在初次公募时只有少量代币了，这种项目本质是中心化项目借用去中心化的流量去割韭菜。为什么一开始就不能以POW的形式去发行，这样每一个币都有成本，且随机。建议大家投资认准纯Pow项目且公开IPO。