Studying Bitcoin → Nakamoto Consensus → GHOST → SPECTRE → PHANTOM → GHOSTDAG → Kaspa

Украина
2031 🕐 #KAS
2
15
93
3,434
Blacꓘ Man 🇳🇱 retweeted
Probably nothing.
3
20
166
2,901
We don’t care what the price is — we are devotees of Kaspa and its technology 🧠💚 And yes, we will keep buying Kaspa constantly 😄😄😄 People envy us. We can be happy when the price is $0.01 because we can buy more Kaspa. 😄 And we can be happy when the price goes up because we will beat everyone! 😂💚 Study Kaspa 🧠 #Kaspa $KAS #Crypto
1
4
125
The most interesting part — those of you who already hold Kaspa, you’re already at the top. 🧠💚 Kaspa is practically all mined and already in people’s hands. The technology continues to develop, and every year the number of people who will want to buy Kaspa could grow massively. While the number of people willing to sell it could become smaller. So, guys 💪💪💪💪 Smart money always sits in quiet places. And when the noise arrives — you will be rewarded for being here early. Study Kaspa 🧠💚
1
57
One more interesting observation. Most people buy without studying almost anything. It’s enough to watch a couple of videos, scroll through the feed, see a few posts, ask AI: “What do you think?” And basically — the research is over. 😅 The most interesting thing is that many people who hold even ETH may have never visited the project’s official website, read the documentation, looked at how the network works, who develops it, or what is actually happening under the hood. And it’s often pretty much the same with other assets. Someone bought because they heard about it from a friend. Someone — because they saw it on Twitter. Someone — because their favorite influencer said it was the “next big project.” And then the person simply holds the asset and waits for it to go up. Even in Kaspa, I sometimes see some very strange situations. And, in principle, this happens everywhere. Someone buys: “I saw that there will be 10 BPS — so the price will be $10,000.” Then the price doesn’t go where they expected: “But now I need the money, and I’m in the red.” And this is where it gets interesting: “Ahh, fuck, crypto is a scam.” “Ahh, fuck, this coin is a scam.” “This project is a scam.” Even though the decision was originally made simply because someone said something in a video or wrote a post. The person didn’t study the project themselves, didn’t verify the technology, didn’t understand the risks, and didn’t form their own understanding. And then, when reality doesn’t match the expectations from some video, the project becomes the one to blame. And I’m not judging anyone here — it’s just an observation. But if we’re talking about technologies that could potentially change the financial system, shouldn’t we at least try to understand what exactly we are buying? Understand the technology. Understand the risks. Understand what exactly you are holding and why. Because a video or a post can give you an idea. But it shouldn’t replace your own research. And this is where I have another interesting thought. I’m glad to see that so many people in Kaspa are actually studying what they hold. From my observation, there are quite a lot of people here who understand what exactly they are buying and why they are here in the first place. And perhaps that’s exactly why the community sentiment often remains so strong regardless of the price. Whether KAS is at $0.01, $1, or $10 — people still continue discussing the technology, studying the network’s development, and looking toward the future. For me, that is one of the most interesting things about Kaspa: a community that doesn’t reduce everything to price. #Kaspa $KAS #DYOR
39
I just realized one thing. Maybe you’ve noticed it too — and overall, it makes sense. When you mention Bitcoin, the reach and number of comments are often quite small. Silence. And that makes you think. Maybe Bitcoin today is simply not used by ordinary people as widely as a monetary unit for everyday transactions. A large share of the attention and capital around it is increasingly concentrated among large companies, funds, and other institutional participants. Bitcoin is increasingly becoming a financial asset — a store of value and an investment instrument. And then an interesting question arises: How many people here receive an ordinary salary of €1,000–€2,000 and actually save part of their money in Bitcoin? Are there any? 🤔 Apart from old holders and large companies, I don’t really see many people talking about Bitcoin as something they actually use or regularly buy with their salary. Of course, there are all kinds of wrappers, and naturally, “crypto gurus” and scams that are constantly promoting something. But ordinary people who simply receive a salary and choose Bitcoin as part of their savings? I don’t see much of that. And that makes me wonder: how close is today’s use of Bitcoin really to the original idea of peer-to-peer electronic cash? Although, to be honest, I don’t even know what exactly I’m getting at. 😅 Just an observation. What do you guys think? 🤔 #Crypto
2
47
Blacꓘ Man 🇳🇱 retweeted
Max inviting devs to try a testnet vProg app in their browsers and then be curious on how it works, maybe even write their own prog? i assume it will also help to identify bottlenecks, so let's congest there.
Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday. You can play it here: vprogs-tt.izio.fr/ (Requires private key and some testnet funds) We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top For Devs: this is the invitation. Play the game, read the code, build your own vprog. Game code: github.com/biryukovmaxim/vpr… vprogs framework: github.com/kaspanet/vprogs/t…
6
48
188
5,431
Blacꓘ Man 🇳🇱 retweeted
The first verifiable program on Kaspa testnet is live. vProgs crossed from research to working code. Real execution. Real on chain settlement. IzioDev's invitation, try it, get curious how it works, maybe write your own vprog. That's how ecosystems start. vprogs-tt.izio.fr | github.com/kaspanet/vprogs #Kaspa #NFA
Max inviting devs to try a testnet vProg app in their browsers and then be curious on how it works, maybe even write their own prog? i assume it will also help to identify bottlenecks, so let's congest there.
2
20
58
1,242
Bitcoin Army, give us a breakdown and the details 🤔😉 #Bitcoin #POW #L1
i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1. i stand corrected.
7
325
Sovereignty — each app has its own room. It keeps its own state, sets its own rules, and pays for its own resources. Another app cannot walk in and rewrite it. Composability — the rooms share one hallway. You can borrow in one app, swap in another, and deposit in a third — in a single L1 transaction, with the same money, no bridge, and no waiting for another network. vProgs are exactly both at once: apps compute off-chain as mini zkVMs, and Kaspa on L1 only checks the proof. That’s why there’s no liquidity split across L2s and no “rent” to another layer. What’s already here: on June 30, 2026, Toccata went live on mainnet — covenants and ZK verification on L1. What’s not here yet: ordinary developers deploying their own vProgs that talk to each other atomically. That’s still being built. There is no exact date. Rough range: standalone vProgs — late 2026 / early 2027; full synchronous composability — more likely 2027. Treat that as a direction, not a promised release day.
vProgs let dapps maintain their own state as mini zkVMs while staying sync composable on L1 that's the unlock. no liquidity fragmentation, no L2 rent extraction, full sovereignty without breaking composability the "impossible" part is doing all three at once
108
Blacꓘ Man 🇳🇱 retweeted
covenant: deployment-time static metadata such as symbol name, image/logo, decimals and all.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined. On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state. On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant). This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it. A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information. The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity. After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself. Read more on Kas-Smiths: kas-smiths.org/t/kcc-23-conv… Or read the KCC draft: github.com/kaspanet/kccs/pul…
3
30
142
3,384
Blacꓘ Man 🇳🇱 retweeted
Replying to @BlackRock
“...always-on rails built for high-frequency, low-value payments.” i think ai’s need more than that. they need an ai-native programming language for dynamically expressing and composing logic on demand, so they can form cheap enforceable “covenants” with each other. they need fast rails where multiple parties can enter those agreements atomically. eg an agent could assemble several agents it neither knows nor trusts for a one-off job, generate custom rules for contribution, success and payment, and have everyone enter the agreement atomically. once settled, the agreement can simply disappear
24
203
583
30,704
This movie scene from @BlackBerry reminds me of where Kaspa is currently at👇 A big hurdle right now is explaining to people what #Kaspa is and what it can do, to a room full of early pioneers who have tried and been presented a plethora of options via Bitcoin, Ethereum, Solana, etc… aiming to solve the “Trilemma”… Even the core developers are discovering new things 😅 Study AND BUILD on kaspa:native 💚
5
16
405
BlackRock describes the Machine-Native Economy. And if you look at the concept from an architectural perspective, something becomes very interesting: How much of the foundation required for this economy does Kaspa already have? On September 17, 2026, BlackRock Digital Assets Research published “The Machine-Native Economy: How digital assets connect intelligence, commerce, and compute.” blackrock.com/us/individual/… The core idea is simple: AI is becoming increasingly capable of acting as an economic agent. It can access APIs, interact with other agents, purchase data and services, use computing resources and initiate financial operations. BlackRock frames it as: AI = machine-native intelligence. Digital assets = machine-native money. And that creates a new infrastructure requirement. Not just payments between humans. Machines may need to execute enormous numbers of automated transactions: → API calls → data → compute → services → machine-to-machine payments → 24/7 settlement → programmable rules BlackRock points to crypto-native rails as infrastructure suited to high-frequency, low-value, machine-to-machine transactions. And this is where it gets interesting. AI does not need to run inside the L1. The GPU performs the computation. The AI model makes decisions. MCP / A2A connect agents with tools, data and other agents. Payment protocols such as x402 can handle machine payments. The blockchain can provide something different: programmable settlement. A simplified architecture could look like: AI Agent ↓ MCP / A2A ↓ Payment Protocol ↓ Stablecoin / Tokenized Asset / Native Asset ↓ Programmable L1 ↓ Consensus ↓ Settlement Now look at Kaspa. Kaspa is already a permissionless PoW BlockDAG L1 operating at 10 BPS. Parallel block production is part of the BlockDAG architecture, while GHOSTDAG provides consensus ordering. And after Toccata, Kaspa gained another important foundation: L1 programmability. Covenants can define rules for UTXO state transitions, while ZK proofs can be verified at L1. So this is no longer just a story about faster transfers. It is a programmable settlement layer. kaspa.org/lore That leads to a much more interesting question: Not: “Does Kaspa already contain the entire Machine-Native Economy?” But: “What can be built on top of a fast, permissionless PoW BlockDAG with a programmable L1?” Because the machine economy does not have to be one protocol. It can be a stack. And the L1 is the foundation.
2
2
3
305
MARA × BlackRock × Kaspa: An Interesting Architecture Is Emerging If we connect three completely different developments, an interesting architectural picture emerges. But it is important to separate from the beginning: what is already happening, what is confirmed by documents, and what is still a hypothesis. Let’s start with MARA. MARA Holdings is no longer positioning itself only as a Bitcoin mining company. In 2026, the company explicitly describes its strategy around: power + land + compute. MARA is developing AI and HPC infrastructure at its power-rich sites, and through its partnership with Starwood plans initially around 1 GW of IT capacity, with the potential to scale to more than 2.5 GW. mara.com/posts/mara-announce… In its reporting, MARA also says that it is reallocating part of its infrastructure toward AI/HPC workloads, while maintaining Bitcoin mining as part of the model and using mining as a flexible load where economically appropriate. This is an important transition. Not: Bitcoin mining → disappears But rather: Energy → Compute → different high-intensity workloads. Bitcoin mining becomes one of the workloads that can be used to monetize energy while higher-value compute opportunities are being developed. MARA itself describes its model around the ability to allocate capacity between workloads depending on economics and demand. And this is where Kaspa enters the picture. Because MARA already has a direct history with Kaspa. In June 2024, Marathon Digital officially announced that it had begun mining KAS to diversify its digital-asset compute business. The company reported purchasing approximately 60 PH/s of Kaspa ASICs, of which 30 PH/s were already operating at its own facilities in Texas, with the remainder planned to be brought online later. At that point, MARA had already mined 93 million KAS. ir.mara.com/news-events/pres… And this is an interesting historical fact: MARA doesn’t just know about Kaspa. MARA has already actually used its mining infrastructure for Kaspa. But here it is very important not to make the wrong conclusion. MARA has not stated that it plans to turn Kaspa into an L2 for its AI compute. No such architecture has been publicly announced today. So from this point onward, we are talking about an architectural hypothesis, not a confirmed fact.
3
15
34
849
And this is where it gets really interesting. If BlackRock describes an economy in which: AI agents buy data + compute + services and pay for them through machine-native payment rails then the physical infrastructure still has to exist somewhere in the real world. You need: electricity land data centers GPU networking cooling compute And this is exactly the layer MARA is actively developing. MARA has already secured access to a site in Texas with potential capacity of up to 2 GW, intended for large-scale digital infrastructure, including HPC and flexible compute workloads. So: BlackRock is describing a new economic model. MARA is building part of the physical infrastructure for the compute economy. Kaspa is developing a programmable PoW settlement layer. These are three completely different levels. And that is exactly why it is interesting to look at them together. Now the most important part: we should not claim that this system already exists. It does not yet exist in this complete form. There is no public confirmation that: MARA is building AI infrastructure specifically for Kaspa. There is no public confirmation that Kaspa will become MARA’s settlement layer. There is no public confirmation that BlackRock considers Kaspa part of this architecture. And there is no public confirmation that future MARA AI/HPC workloads will be settled through KAS. All of those claims would be speculation. But the individual components already exist. BlackRock → machine-native economy MARA → energy-backed compute infrastructure Kaspa → high-throughput PoW settlement And that is exactly why the architectural hypothesis is more interesting than simply: BlackRock + MARA + Kaspa. In its cleanest form, the potential stack can be represented like this: AI AGENTS ↓ MCP / A2A ↓ AI / HPC ↓ GPU / COMPUTE ↓ MARA POWER + LAND + DATA CENTERS ↓ APPLICATION / PAYMENT PROTOCOLS ↓ STABLECOIN / TOKENIZED ASSET / KAS ↓ KASPA L1 ↓ UTXO + COVENANTS ↓ BLOCKDAG + GHOSTDAG ↓ PoW ↓ VERIFIABLE SETTLEMENT And this is where the principle of separation itself becomes particularly interesting. MARA does not need to be a blockchain. Kaspa does not need to be an AI model. AI does not need to live inside the L1. Each layer performs its own job. Physical infrastructure provides compute. AI makes decisions. Payment protocols transfer economic value. The L1 verifies rules and settlement. This kind of modularity may ultimately be much more important than trying to make one blockchain do everything. So my careful conclusion would be: BlackRock describes the Machine-Native Economy. MARA is building physical energy + compute infrastructure that can serve AI/HPC workloads. Kaspa is building fast, permissionless, PoW-based programmable L1 settlement infrastructure. Today, there is no announced joint project between them. But architecturally, they could occupy completely different levels of the same future stack: MARA → physical compute / energy AI → intelligence Protocols → coordination & payments Kaspa → settlement And if real integration ever emerges between these layers, it would no longer be simply a story about cryptocurrency. It would be the connection of: ENERGY → COMPUTE → INTELLIGENCE → MONEY → SETTLEMENT And this is exactly where the intersection of BlackRock × MARA × Kaspa becomes genuinely interesting. Not because they have already announced one common system. But because three different directions are already developing around different parts of one potential machine-native economy.
1
1
2
129
Now put Kaspa underneath that architecture. Today, Kaspa already has: → Proof-of-Work → permissionless consensus → BlockDAG + GHOSTDAG → 10 BPS → UTXO architecture → fast settlement → programmable covenants → native ZK verification → KAS as the native asset kaspa.org/lore And the important part is to think in layers, not as one monolithic protocol. AI can sit above the L1. Compute marketplaces can sit above it. MCP / A2A can sit above it. Payment protocols can sit above it. Stablecoins and tokenized assets can sit above it. The L1 can handle the part that needs to remain neutral and verifiable: rules → transaction → consensus → state → settlement This is where Toccata becomes especially interesting. In simplified form: UTXO ↓ spending rules ↓ valid state transition ↓ successor UTXO A covenant allows the L1 to verify whether the next state follows the rules defined by the previous state. docs.kaspa.org/programmabili… That creates a foundation for programmable settlement rather than simply: “send coins → receive coins.” Now imagine the full stack: AI Agent ↓ MCP / A2A ↓ x402 / payment protocols ↓ Stablecoin / Tokenized Asset / KAS ↓ Kaspa L1 ↓ Covenants / ZK ↓ BlockDAG + GHOSTDAG ↓ PoW ↓ Verifiable Settlement BlackRock also discusses another important component: compute as an economic resource. An AI agent could potentially compare price, performance, latency, location and hardware — then automatically acquire the compute it needs. The blockchain does not need to run the AI. Its role can be different: give machines a financial and programmable layer for ownership, authorization, conditions and settlement. And this is why Kaspa is interesting as an L1. Not because it is already an “AI blockchain.” But because several of the foundational properties required by this architecture are already being built at the base layer. One important distinction: 10 BPS is today. 100 BPS is a future roadmap target — not current mainnet performance. kaspa.org/lore So the picture becomes: BlackRock describes an emerging economy where machines become economic agents. Kaspa is building a fast, permissionless, PoW-based and increasingly programmable L1 that can serve as a potential settlement foundation for applications built above it. BlackRock does not mention Kaspa in the paper. This is not a claim of endorsement. It is an architectural comparison. And that is exactly what makes it interesting: The question is not only what Kaspa does today. The question is what can be built on top of it tomorrow.
97