

CryptQ 𐤊.
7.2K posts





@grok There is absolutely no way that they got higher revenues and were able to “balance the budget”. Every state, city and town across the United States are in budget trouble so interrogate your own contentions. After vigorously interrogating your own contentions tell me and explain to me what they really did to try and make it appear that they are in a better budget situation then they are actually in.





What we think we hear you saying @hashdag is that while some people in the ecosystem are focused on bringing existing DeFi activity onto #Kaspa, you are focused/exploring something bigger: Using Kaspa as infrastructure for large-scale coordination systems. Not just trading coins or moving liquidity around, but enabling people, businesses, machines, and eventually AI systems to coordinate actions, commitments, resources, and decisions in real time through a decentralized ledger. That could eventually impact areas like: • AI agent coordination • logistics and supply chains • distributed compute markets • energy balancing systems • prediction and assurance markets • machine-to-machine economies • dynamic resource allocation • decentralized scheduling systems • reputation and verification systems • real-time enterprise coordination This is something @Kaspa_Commons has been talking about for quite some time as well. The idea that Kaspa’s long-term opportunity should extend far beyond traditional crypto finance and into real-time decentralized coordination across industries, systems, and emerging machine economies. More thoughts in thread... #PoweredByKaspa #KaspaCoordination


What we think we hear you saying @hashdag is that while some people in the ecosystem are focused on bringing existing DeFi activity onto #Kaspa, you are focused/exploring something bigger: Using Kaspa as infrastructure for large-scale coordination systems. Not just trading coins or moving liquidity around, but enabling people, businesses, machines, and eventually AI systems to coordinate actions, commitments, resources, and decisions in real time through a decentralized ledger. That could eventually impact areas like: • AI agent coordination • logistics and supply chains • distributed compute markets • energy balancing systems • prediction and assurance markets • machine-to-machine economies • dynamic resource allocation • decentralized scheduling systems • reputation and verification systems • real-time enterprise coordination This is something @Kaspa_Commons has been talking about for quite some time as well. The idea that Kaspa’s long-term opportunity should extend far beyond traditional crypto finance and into real-time decentralized coordination across industries, systems, and emerging machine economies. More thoughts in thread... #PoweredByKaspa #KaspaCoordination



eufactcheck.eu/factcheck/true… <- 2020 artical since 2014? 1. The Swedish Chip and the "Mark" The news of Sweden’s microchip implants (RFID/NFC) for ID and payments is the physical manifestation of Revelation 13:16-17. The Scripture: "And he causeth all... to receive a mark in their right hand... that no man might buy or sell, save he that had the mark." The Observation: This isn't "prophecy" anymore; it is a Condition of Reality. The Old System (Sand): Wants the "Mark" to be Biological(your hand/your chip). It wants to put the "Sudo key” or "Administrative Hegemony" tech words for control!! Inside your body. If the control is tech into flesh the counter is also tech outside the flesh. Another way to see this is "Centralized Admin Key" or "Permissioned Backdoor." The New System (Rock): Keeps the "Mark" Mathematical (your private key/your seed). It keeps the "knowing" in your spirit. Tangem(Cold Wallet) - Kaspa 2. The Templar Image: "More Extreme in My Religious Beliefs" The image of the Knight Templar "New Man" (Ephesians 4:24) armor. The Consideration:"Extreme" in this sense doesn't mean violence; it means Uncompromising Truth. It is the shepherd refusing to look into the Pool of Theft & Become It. In the King James Version (KJV), Ephesians 4:22–24 presents a complete three-step process for spiritual transformation: Verse 22 (The Removal): "That ye put off concerning the former conversation the old man, which is corrupt according to the deceitful lusts; Verse 23 (The Renewal): "And be renewed in the spirit of your mind; Verse 24 (The Restoration): "And that ye put on the new man, which after God is created in righteousness and true holiness. Key Terms Explained "Former conversation" This refers to your previous conduct or lifestyle before following Christ. "The old man": The corrupt, sinful nature inherited from Adam that is driven by desires that deceive you into thinking they will bring happiness. "Renewed in the spirit of your mind": This is a continuous process where your thoughts and attitudes are transformed to align with God's truth. (The Logos) John 1-14 KJV. "The new man": The regenerated nature created in the image of God, characterized by genuine uprightness and purity. My observable logic: The Swedish chip fits the pattern of increasing convenience tied to digital identity and payment control. That is observable. It is a choice right now (voluntary implant). The Bible describes a future system where it becomes mandatory (no one can buy or sell without it). That part has not happened yet.(CBDC Alert) Humans have always moved toward more efficient control systems. The Bible documented it & repeatedly warns about the danger of that path when it replaces trust in God. So yes my final SHARP end, the Swedish chip is observable evidence of the direction humanity is heading towards and this sentance show my thoughts on this subject. [convenience + control through technology in the hand]. Study $kas


Trump lands in China with Elon Musk, Nvidia’s Jensen Huang, Marco Rubio, Pete Hegseth, Eric & Lara Trump. This delegation hits different. First Beijing visit in 9 years. Biggest question: Does this summit cool global markets or crank up the heat on Iran?



The upcoming upgrade was chosen without regards to vprogs, and no meaningful effort was made to optimize it for vprogs (definitely nothing delaying Tocatta by more than a few days). Tocatta is a principled implementation of bitcoin-originating covenants which, if ever implemented in bitcoin, would use the op_cat workaround. It is the default method to introduce programmability into a thin verification-oriented L1 to preserve its decentralized lean value prop. vprogs are outside core’s focus precisely because we are optimizing for usability over theoretical superiority. I hope this helps you and grok update your premise. (BTW counterexample to your claim about inevitability of fragmentation: Solana)




I did not follow the full convo, but a few clarifications came to mind from the parts I did read. 1. @maxibitcat’s idea of “ordering of this type of transaction only at merge time, using some randomness coming from the whole round” obviously requires a consensus change. btw I’d apply it to all txs in order to reduce MEV also for based apps etc. 2. there is a ladder here: step 1 (what I referred to in the main post): non-consensus change that can be implemented post Toccata activation: accept the tx to the mempool without resolving the shared-state UTXO (call this abstract entity X). when building the block template, resolve to the most updated UTXO of X. requires indexing the UTXO set by covenant ids. con: parallel miners can resolve different txs to the same UTXO so some of them will not count (effectively serializing access to X to 1 per round). step 2: a future consensus change that resolves X at block merge time according to the final mergeset order. as I’ve told bitcat, this would break fundamental assumptions of the UTXO model and I highly doubt we can do this. eg it breaks the linkage between a tx id and the UTXOs the tx spends (in graph terms it breaks the hashable edge structure of the tx DAG). step 3 (independent of 2): randomize the per-round order and don’t give the merging block full control. relevant to any MEV-hardness claim over Kaspa. 3. interestingly, step 1 does not allow easy front-running and sandwiching. that’s bcs Kaspa rules forbid chained txs within the same block, so the miner can’t have both his tx and the attacked tx in his block (the latter must use the output of the earlier as input).

