Kaspa https://kaspa.org/ Proof-of-Work Cryptocurrency with GHOSTDAG protocol - Maintained, with love by Community Members. Mon, 09 Jun 2025 21:46:49 +0000 en-US hourly 1 https://i0.wp.com/kaspa.org/wp-content/uploads/2023/06/cropped-Kaspa-Icon-Dark-Green-on-White.png?fit=32%2C32&ssl=1 Kaspa https://kaspa.org/ 32 32 205134466 Interview with Developer FreshAir https://kaspa.org/interview-with-developer-freshair/ Mon, 02 Jun 2025 19:35:28 +0000 https://kaspa.org/?p=53322 Tell us a bit about yourself. (background, work experience, intro to KASPA,etc) I am a fresh M.Sc. in computer sciences with a focus in cryptography. I’ve known Shai from academy […]

The post Interview with Developer FreshAir appeared first on Kaspa.

]]>
Tell us a bit about yourself. (background, work experience, intro to KASPA,etc)
I am a fresh M.Sc. in computer sciences with a focus in cryptography. I’ve known Shai from academy and first heard about Kaspa through him, but took my time in getting in.

What drew you to work on Kaspa technology?
I used to look down on the crypto industry, for the same reasons many do. In university I did glance at cryptocurrencies from an academic perspective, but it only strengthened my view that it all sits on shaky foundations—and having to wait 1 hour to be sure a transaction won’t be reversed didn’t make an impression on me as a real competitor to fiat. When I heard of Kaspa,I was skeptical for these reasons, but followed from a distance. I mostly became impressed with the academic approach to what I saw as a “wing it” type of industry. And yeah, I loved seeing the math I learned in academy, being applied to real world use cases, that people truly care about.

What has been your key role in the Kaspa community?
My main focus currently is on R&D of the Kaspa smart contracts infrastructure. That is, enabling based rollups/daos/meta SC (pick how you want to think of these) to deploy on top of Kaspa, relying on Kaspa’s security and decentralization for sequencing their transactions, while keeping their interpretation of the transaction anchored in Kaspa via zk proofs of the execution of these transactions by order. I am currently working a lot on how interoperability should look between these many “L2”, to prevent the dreaded fragmentation problem.

You received a research/dev grant from KEF. Can you explain what that was, why you applied, what does it entail? Are you focused on Kaspa core network, or is it generalized work that any development team could implement?
After a long time spent on discord, I knew I had a good grasp of the theory, and made a leap of faith. I started learning rust. When I finished going through the rust book, I got in touch with Michael and Yonatan and asked how I can help Kaspa. With their guidance, I simultaneously started coding (KIP6) and researching (oracles at the time) for Kaspa. After a while, I asked Yonatan if there is a way I could continue what I do while having financial stability. Yonatan suggested KEF could help out with a research grant, and from there I got in touch with Monica and Junny. We all jointly decided Kaspa needs at the moment more manpower on the smart contracts infrastructure design, so that became the focus.

Kaspa is aiming to solve real world problems. Utility and every day use adoption is the goal. Verses personal wealth making and get rich schemes, typical to cryptoland themes for 15 years.Tell us how your work will help this mission.
“Complex” finance at times looks boring, but it had a role in our modern world achieving what it has. At the moment, these complex functionalities are usually limited to brokers and corporations. The common folk are excluded from this game. A case could be made that it is exactly because we are so unfamiliar with that world, that we usually find it boring.

Defi thus far has not really managed to be simultaneously decentralized and functional at scale. Kaspa, unhindered by the common problems of throughput limitation and slow confirmations, could be the first to democratize complex financing.

What are you most looking forward to as it relates to Kaspa global adoption mission. Where do you see groups/projects like Kii and KEF helping in this?
I hope to see more and more foundations step in to help Kaspa achieve its calling. Supporting devs is important and vital, but I guess another thing I’d like to see is more encouragement for people and corporations to use and accept Kaspa. Kaspa is very convenient and can be an amazing pay on the spot method. I work on SC, but I first and foremost think of Kaspa as a payment method. Time will tell.

Whats is your take on the Kaspa community, culture/environment that has been created these past 3.5 years? Any shout outs? 🙂
I mostly hang around in the Kaspa discord. I enjoy seeing the unmediated interface between common folk from all backgrounds and ivory tower academics. It’s something that I don’t think exists in many other fields. It’s fascinating to me to see how people evolve with time and learn more and more of crypto-myself included.
I don’t know for certain, but to an extent, I think this is unique for the Kaspa community, because without over-romanticizing, we are very much more tech oriented, and on good days at least, can even take a well constructed criticism.

The post Interview with Developer FreshAir appeared first on Kaspa.

]]>
53322
Eliott, a Rising Young Star in the Blockchain(DAG) Space https://kaspa.org/eliott-a-rising-young-star-in-the-blockchaindag-space/ Tue, 27 May 2025 13:26:10 +0000 https://kaspa.org/?p=53405 The post Eliott, a Rising Young Star in the Blockchain(DAG) Space appeared first on Kaspa.

]]>

I caught up with Eliott, a rising young star in the blockchain space and newest recipient of a KEF Grant to further research and develop for Kaspa!

Chad: Hi Eliott, congratulations on the KEF grant! Can you briefly introduce yourself and tell us what you are up to with this work?

Eliott: Thank you! It’s a pleasure to be back working in crypto. I’m a Pure Mathematics Master’s graduate from ETH Zurich, where I first explored crypto through my thesis on oracles, supervised by Yonatan. I’m passionate about crypto because it allows me to tackle complex, theoretical mathematics while contributing to enhanced security and innovation in blockchain protocols. Applying my studies to crypto, specifically oracles, MEV, and markets, has been the first time I’ve felt I truly understand the purpose of my theoretical studies. I spent six months in banking in 2024, as I wanted to understand how banks worked and how they moved the economy. However, I quickly found the work unchallenging and misaligned with my values—I wasn’t proud of my contributions to society. So, I’ve been eager to return to working with Yonatan for some time now, as his philosophy very much aligns with my own.

*MEV resistance is a defence against “maximal extractable value” (MEV) attacks on crypto transactions. MEV is a hidden fee that can affect the price of transactions and lead to failed trades.

I’m currently working on oracles, MEV, and decentralized exchanges. These three topics are closely related and essential for security, exchanges, and fairness. Oracles are crucial for blockchains to function in real-world scenarios; for example, price oracles secure billions in TVL for DeFi platforms like Aave. However, during my thesis, I noticed academia lacks focus in this area, just as it does in MEV solutions. I want to tackle the challenge of designing better solutions to create more transparency and fairness in the underlying mechanisms of DeFi.

*Aave Pronounced (A-vey) Greek word meaning “Ghost.”
It is is an open-source, non-custodial protocol that allows people to lend and borrow cryptocurrencies through decentralized finance (DeFi). Essentially, it provides a peer-to-peer money market for cryptocurrencies, removing financial middlemen from the equation.

I will also start posting on Medium (@noclue122) once I consider my expertise sufficient to express myself without making too many mistakes. I’d like to share aspects of my work, and improve awareness about unresolved challenges, and how we are working towards solving them. This approach is highly motivated by reading Shai’s work, which got me into Kaspa in the first place. His Medium posts made me realize I could understand some mechanism behind crypto, which at the time seemed like an obstacle. That is what sparked my interest in the field.

Chad: Will your work be on Kaspa core network, or is it generalized deep work that any development team could implement?

ELIOTT:  Technically, any team can implement this work once the research is published, as others can adapt and integrate the findings. My goal isn’t to gatekeep research but to advance academia, so I’m all for other teams using it to address existing challenges. However, as Sutton recently noted on X, multi-leader consensus is critical for robustoracles and MEV resistance, and we’re designing our oracle with this principle in mind.

Yonatan gave a great explanation during his talk, highlighting that no matter how good an oracle is, it often ends up centralized. A single consensus validator is relied upon to deliver the oracle price on-chain and could arbitrarily manipulate or censor it. Similarly, many attempted solutions for MEV front-running exist, but the final consensus leader can choose the transaction order, allowing them to censor transactions even in designs that prevent front-running (see Budish’s HFT arms race). Kaspa’s architecture makes the foundation of this work much easier and will certainly enable a superior design.

Chad: We Asked CHatGPT to explain Yonatan’s tweet on Oracles to an eighth grader.

The Problem:
Imagine you’re playing a game where you have to guess the price of candy from a store. You ask your friend (the oracle) to check the price online and tell you. But what if your friend lies or makes a mistake? That’s the oracle problem — you can’t be sure the information you’re getting is true.

Why Is This a Big Deal in Crypto?
In cryptocurrency, blockchains (like Ethereum) sometimes need real-world information, like the price of Bitcoin, to do things like process payments or trades. The problem is — who provides that information (the oracle)? If the oracle lies or is slow, people could lose money.

Two Scenarios:
1. The Easy-to-Catch Cheater (Good)
Suppose a company controls a bridge between two blockchains. If they cheat by changing the balance or lying, everyone can immediately see the lie and stop using the bridge. The cheater gets caught once and loses everything.
2. The Sneaky Cheater (Bad)
Now imagine the same bridge but with a central oracle providing data (like prices). If the oracle gives wrong prices (even by accident), it’s hard to prove if they did it on purpose or if it was just a bad internet connection. This makes it impossible to hold them accountable — meaning they could cheat slowly without getting caught.

The Solution (Maybe):
The person tweeting suggests using a group of miners (like people voting) to estimate the correct information — like a group of friends guessing the candy price instead of just one friend. This way, it’s less likely someone could cheat. The method would rely on majority honesty — the same way mining in Bitcoin works.

But to make this work, you’d need super-fast mining (many blocks per second), so the information stays fresh. That’s why PoW-DAG (like Kaspa) was mentioned — because it’s really fast and could help solve this problem.
Bottom Line:
• It’s easier to catch a company lying about money than to catch a company slowly feeding wrong information.
• Using many miners to agree on information (like the price of candy) might solve the problem — especially if the network is super fast.
• The person tweeting thinks fast PoW-DAG networks like Kaspa might help solve this big problem in crypto.

This is basically about truth in information and how hard it is to prove if someone is lying — especially when you rely on them for data.

ELIOTT: I think it’s crucial to help everyday users understand how oracles matter in crypto. ChatGPT did a good job breaking it down. The core challenge with oracles is figuring out the “real” price of an asset. But since no one knows the absolute “truth” (as it’s the whole point of the oracle in the first place), lies can be hard to spot—especially when your idea of the truth is influenced by those lies. That’s why penalizing false inputs is so tricky.

Take Aave, a DeFi lending platform. If someone can manipulate an oracle’s price feed—even for a moment—they could liquidate your loan unfairly. For instance, if Aave’s oracle only pulls data from MEXC and MEXC’s liquidity dries up (because not your keys not your coins), attackers can sell Kaspa heavily there, push the price down, and trigger liquidations—even if other exchanges still show a fairer price. This is how poor oracles create unfair outcomes and MEV opportunities.

When reading whitepapers of current oracle protocols, I find the proofs lacking. Claims are made like “participants will behave like this” without any mathematical modelling or proofs. This is a bit frustrating as my whole studies have been based around getting zeros when my proofs were lacking. It doesn’t sit right with me, billions are secured on these protocols that rely on assumptions, and unproved claims. I’d like to change that.

Chad: Kaspa solving real world problems is the main message for Kaspa onward. Utility and every day use adoption. Kaspa integrated into The IoT, etc. What are your thoughts on this?

ELIOTT: In crypto, there’s no truly great oracle solution yet—most rely on claims of security with no mathematical proofs, and make assumptions that won’t necessarily hold. For example, every current oracle solution assumes that there is at least 50% of participants that will be honest. And I explained in this X thread why this doesn’t necessarily hold. As long as this problem is set aside, the blockchain will rely on trust, that Chainlink nodes won’t one day have an incentive to lie, or a validator to censor the on-chain delivery. It’s a real world problem, and it isn’t talked about enough.

I’d like to design an oracle solution, MEV and trading designs that have the same level of beauty as Dagknight. This challenge will probably take a while given I have only been in crypto research for a year now, but I think the experience will be memorable.

MEV resistance is a defense against “maximal extractable value” (MEV) attacks on crypto transactions. MEV is a hidden fee that can affect the price of transactions and lead to failed trades.

X: @elimmea
LinkedIn: linkedin.com/in/eliott-mea           

 

The post Eliott, a Rising Young Star in the Blockchain(DAG) Space appeared first on Kaspa.

]]>
53405
Why Kaspa Succeeds Where Millions of Crypto Projects Have Failed https://kaspa.org/why-kaspa-succeeds-where-milliona-of-crypto-projects-have-failed/ Wed, 21 May 2025 13:39:01 +0000 https://kaspa.org/?p=53280 The post Why Kaspa Succeeds Where Millions of Crypto Projects Have Failed appeared first on Kaspa.

]]>

In response to CoinGecko’s Article — “Dead Coins: Over 50% of Cryptocurrencies Have Failed”

The cryptocurrency landscape has witnessed a significant number of project failures, with over 50% of all cryptocurrencies launched and listed since 2021 no longer actively trading. According to a recent report, out of nearly 7 million cryptocurrencies listed on GeckoTerminal, approximately 3.7 million have failed. Notably, the first quarter of 2025 alone accounted for 1.8 million of these failures, representing nearly half of all recorded project closures, the highest number of failures recorded in a single year.

According to Tangem: As of May 2025, there are over 37 million crypto tokens, and we’re on track to reach 100 million by the end of 2025. For context, there were fewer than 3,000 tokens in 2017–2018 and less than 500 in 2013–2014. How Many Cryptocurrencies Are There in 2025

Given the vast number of tokens created and the high attrition rate, it’s estimated that only a small fraction—possibly less than 0.1%—remain active or have any meaningful trading activity.

Common Factors Leading to Cryptocurrency Failures

  • Lack of Utility or Purpose
    Many failed projects lacked a clear use case or failed to deliver on promised functionalities, leading to diminished interest and eventual collapse.
  • Scams and Fraudulent Schemes
    Projects like Bitconnect operated as Ponzi schemes, offering unsustainable returns and eventually collapsing under regulatory scrutiny and loss of investor confidence.
  • Regulatory and Legal Challenges
    Initiatives such as KodakCoin faced regulatory hurdles and questions about their legitimacy, leading to indefinite delays and eventual shutdowns.
  • Security Vulnerabilities
    The DAO, an early decentralized autonomous organization, suffered a significant hack due to code vulnerabilities, resulting in substantial financial losses and a controversial hard fork of the Ethereum blockchain.
  • Market Saturation and Low-Quality Projects
    The ease of creating new tokens, especially with platforms like pump.fun, led to a flood of low-effort projects, many of which lacked substance and quickly failed.

Common Traits of Successful Cryptocurrencies

  • Strong Community Engagement
    Projects with active and engaged communities tend to have greater resilience and staying power. These communities, comprising users, developers, and investors, play a crucial role in promoting the cryptocurrency, providing feedback, and fostering adoption.
  • Clear Use Cases
    Cryptocurrencies that address real-world problems or offer unique value propositions are more likely to succeed. Whether it’s facilitating decentralized finance (DeFi), enhancing supply chain transparency, or enabling NFT transactions, a well-defined purpose resonates with users and investors.
  • Robust Technology and Security
    Projects that prioritize technological robustness and security are better positioned for long-term success. For instance, Firo (formerly Zcoin) implemented advanced privacy protocols like Lelantus Spark and addressed security challenges proactively.
  • Grassroots Community and Brand Building
    Coordinated efforts around early brand building, grassroots outreach, consistent messaging, peer-to-peer education, and no hype.

The Success or Failure of a Cryptocurrency Project Hinges on Several Factors

  • Utility and Purpose
    Projects must address real-world problems or offer unique value.
  • Community Engagement
    Active and supportive communities can drive adoption and resilience.
  • Technological Robustness
    Security and reliability are paramount.
  • Regulatory Compliance
    Navigating legal landscapes is crucial for longevity.
  • Market Differentiation
    In a saturated market, standing out with quality and innovation is essential.
  • Compelling Brand Building
    Strong brand story and brand building with a peer-to-peer education and adoption approach.

Understanding these factors can provide valuable insights for investors and developers aiming to navigate the complex world of cryptocurrencies.

Marketing Traits in Failed Projects

  • Overhyped, Under-Delivered
    Projects like Bitconnect and SafeMoon used exaggerated promises (e.g., “guaranteed returns”, “to the moon” slogans). This kind of hype attracted short-term investors, but collapsed when the tech or tokenomics failed to back it up.
  • Celebrity Shilling Without Substance
    Endorsements from influencers or celebrities (e.g., Floyd Mayweather, DJ Khaled) led to short-term pump-and-dump schemes.
  • Expensive Ad Buys and Paid Public Relations by Third-Party Companies (Not Part of the Community)
    Without real utility, these coins lost value once public interest faded.
  • Lack of Target Audience Understanding
    Many projects launched with vague or generic messages, which failed to articulate a unique reason to exist. Tokens like KodakCoin tried to capitalize on buzzwords (e.g., blockchain + photography) without a real strategy.
  • No Post-Launch Marketing Plan
    Projects that spent heavily on ICO hype but went silent afterward often lost momentum and investor confidence.

Kaspa’s Success

Transparent, Developer-Led Communication

Kaspa’s lead developers and researchers are publicly known, frequently communicating on X (Twitter), and openly discuss challenges, milestones, and ambitions via AMAs, videos, and conference keynotes. The open-source nature of Kaspa’s development invites scrutiny and collaboration, strengthening credibility.

Understated, Yet Strategic Branding

The simple, yet iconic logo and brand narrative stands out in the sea of other coins and tokens.
Real-world adoption narratives like The “Kaspa Accepted Here” initiative builds real-world adoption at the grassroots level, one merchant at a time.
The “Powered by Kaspa” initiative flips the coin to focus on enterprise markets looking for a powerful, decentralized DLT (Distributed Ledger Technology).
No ICO. No flashy launch. No empty promises — just steady, transparent rollout and growing real-world relevance.

Long-Term Vision Over Hype

Kaspa’s outreach narrative focuses on both the currency and DLT layers for the digital future, not a fleeting trend. Its monetary policy is fixed and simple, appealing to those tired of manipulated tokenomics and rug-pull mechanics. The focus on infrastructure, not speculation, gives Kaspa a foundation similar to Bitcoin — but with modern capabilities.

Community-Driven and Organic Growth

Kaspa’s marketing is bottom-up, not top-down.
The community is the core marketing engine — creating articles, creative educational content, explainer videos, and grassroots campaigns with consistent support from coordinated daily efforts by the Rhubarbarians and the CMF (Community Marketing Fund). This builds authentic engagement and avoids the artificial hype seen in many failed tokens. Instead of influencer-driven pumps, Kaspa has cultivated a loyal and technically-literate base that amplifies its strengths.

Projects like SafeMoon leaned heavily on influencer hype and flashy promises, with little community depth beyond price speculation.

Value-First Messaging

Kaspa doesn’t advertise price narratives. Instead, it leads with proven technological features:

  • Instant transaction finality
  • High throughput (10+ BPS)
  • Scalability via blockDAG architecture
  • Permissionless monetary network

Kaspa ships when it’s ready. It has long proven its slow and steady philosophy, delivering on all tasks with no stalls, no downtimes and a consistently improved network.

This appeals to developers, entrepreneurs, and long-term users — not just traders.

Many defunct coins marketed unrealistic financial returns or chased fads without backing utility or bridging to the existing TradFi system, and ignored sustainable, stable DeFi solutions.

Why Kaspa is Succeeding

Kaspa avoids the traps that killed thousands of coins — overpromising, underdelivering, hype with no utility. Instead, Kaspa focuses on the technology, while its marketing and narrative emphasize credibility, community, and capability — which is exactly why it’s still growing while most others have failed.

Kaspa distinguishes itself in the cryptocurrency landscape through a combination of technological innovation, transparent leadership, community-driven marketing, and real-world applicability.

These factors collectively contribute to its resilience and growth, contrasting sharply with the multitude of projects that have faltered.

Technological Innovation and Real Utility

Many failed projects lacked substantive technological foundations or failed to deliver on their promises. Kaspa, however, offers:

  • BlockDAG Architecture: Enables high throughput with 10+ blocks per second, facilitating rapid transaction confirmations.
  • Instant Confirmation and Finality: Transactions achieve finality within seconds, enhancing user experience and trust.
  • Scalability: Designed to scale without compromising decentralization or security.

Transparent Leadership and Open-Source Development

Transparency is pivotal in building trust within the crypto community. Kaspa’s development is led by highly-documented academic and respected figures in blockchain research, ensuring credible leadership where they are publicly known and academically recognized, fostering confidence among users and developers. Through its open-source culture, Kaspa encourages community contributions and scrutiny, enhancing the project’s robustness.

Community-Driven/Non-Traditional Marketing

Kaspa’s growth is also propelled by its community through:

  • Grassroots Engagement: Community members actively create educational content, promote adoption, and support development. There are 1000’s of Kaspa content creators on X, YouTube.  (Kaspa_Commons follows many of them and more each day, so please support these amplifying Kaspa daily!)
  • Authentic Promotion: Relies on organic growth rather than paid endorsements or hype-driven campaigns.
  • Quality and Consistent Messaging: Simple, quality, and contextualized messaging. Community-driven content expands as the project matures.

Sound Economic Model

Kaspa employs a straightforward and transparent economic model:

  • Fair Launch: No premine or initial coin offering, ensuring equitable distribution.
  • Predictable Emission Schedule: Similar to Bitcoin’s deflationary model, with a more rapid emissions schedule, providing long-term value stability.

Real-World Applicability and Adoption

Kaspa focuses on practical use cases:

  • Local Merchant and Enterprise Adoption: Initiatives like “Kaspa Accepted Here” and “Powered by Kaspa” promote real-world usage.
  • User-Friendly Tools: Easy-to-use wallets and integration options to facilitate everyday transactions.
  • Attracting Developers and Real-World Markets: Amplifying developer opportunities through the core project or via foundations like the Kaspa Ecosystem Foundation — inviting them into its ecosystem early on to build the next generation of DApps for DePIN, RWA, and DeFi. Pushing the boundaries of real-world adoption through initiatives like the Kaspa Industrial Initiative.
  • Special Thanks to Kasplex, IgraLabs and other developers joining the project and building out the ecosystem

This practical approach ensures relevance and utility, unlike many projects that failed to move beyond speculative trading.

Kaspa’s continued success is attributed to its commitment to technological excellence, transparent governance, community engagement, sound economics, and real-world utility. These elements collectively foster a sustainable and trustworthy ecosystem, setting it apart from the multitude of projects that have failed due to lack of substance, transparency, and utility.

The post Why Kaspa Succeeds Where Millions of Crypto Projects Have Failed appeared first on Kaspa.

]]>
53280
Kaspa Updates to Crescendo and 10BPS https://kaspa.org/kaspa-updates-to-crescendo-and-10bps/ Mon, 05 May 2025 21:24:59 +0000 https://kaspa.org/?p=53214 The post Kaspa Updates to Crescendo and 10BPS appeared first on Kaspa.

]]>

This event marks the culmination of nearly three years of monumental effort by the core development team, who have undertaken a complete architectural redesign and rewritten Kaspa’s core code from Golang to Rust, focusing on performance optimization across all possible fronts simultaneously. Thanks to this feat, Kaspa will become, by a wide margin, the fastest pure Proof-of-Work (PoW) coin in history, while maintaining the highest level of decentralization and transaction processing and confirmation speed in a permissionless, asynchronous system.

Moreover, this block generation speed, combined with linking blocks not in a chain but in a directed acyclic graph, creates a truly unique multi-leader consensus mechanism. This consensus has the potential to serve as the foundation for achieving the holy grails of crypto: a security budget, MEV (Miner Extractable Value) avoidance, and the implementation of reliable decentralized oracles.

At the same time, the code is written in such a way that running a full Kaspa node is possible on ordinary household PCs with standard internet connections, which is itself a unique feature for crypto projects offering this level of capability. It fully aligns with, and realizes in practice Satoshi’s vision of complete autonomy and self-sovereignty for every network participant, from large corporations and governments to ordinary individuals.

Last but not least, a new WASM interface for RPC requests was created along the way, greatly simplifying how wallets and apps interact with Kaspa nodes. It sparked a surge in Kaspa-compatible wallets, thanks to the sub-team that simultaneously worked on the node’s WASM subsystem and developed the Kaspa-NG wallet (https://kaspa-ng.org/) to replace the retiring Kaspa web and KDX wallets. People are gathering to watch and celebrate the transition online, so join us:

If, for some reason, you haven’t yet upgraded to the hardfork-ready node version, here’s the link to it: https://github.com/kaspanet/rusty-kaspa/releases/latest, and here’s the link to the post-fork working version of the Kaspa-stratum bridge which enables solo mining: https://github.com/aglov413/kaspa-stratum-bridge/releases/tag/v1.3.0

Today, without any doubt, will go down in crypto history as the day when the efforts of human intellect once again proved that the bastions of what seemed impossible inevitably fall under the pressure of talent and selfless dedication!

_____________________________________________________________________________________

X Post excerpts from Lead Developer, Michael Sutton about Crescendo

Kaspa’s 10 bps crescendo upgrade, activated today on mainnet, allows the innovation and scalability of the Ghostdag protocol (@hashdaget al) to truly shine for the first time. While the theory behind this multi‑leader, parallel‑structured DAG protocol has been implemented at 1 bps as well, a 1000‑millisecond block time is still sufficiently above modern internet RTT; thus, by tightening latency and network assumptions one can imagine a linear blockchain structure at 1 bps as well (cf. Solana’s 400 ms block time with a linear structure). Increasing the block rate to 10 per second, achieved by reducing block time to 100 ms (< 200 ms ≈ global RTT), can only be secure with a consensus protocol that inherently allows parallelism = multi‑leader consensus. Passing the RTT threshold is thus a qualitative, not merely a quantitative, leap. Link

A brain dump of all things crescendo, what’s included, what are the benefits… Link

Increasing the block per seconds from 1 to 10 bps while keeping block capacity ~fixed (more on that later). Throughput: obviously, transaction throughput increases. How much? almost tenfold but not exactly 10x. Having more parallel blocks increases the collision rate to some degree.

On TN10 and with current mempool txn selection policy, we observe ~80-90% efficiency (i.e., 80-90% of the txns are unique). If the mempool gets over congested and demand significantly exceeds capacity, this efficiency value goes towards 100%. So to conclude, TPS is increasing 8-9x. The missing info is mainnet average DAG width post-activation vs. today. Mempool policies can be finetuned in the coming future without a hardfork based on such real-world data. Frequency: average block time (=interval between blocks) is being reduced from 1 second to 100 milliseconds. This means blink-of-an-eye txn inclusion time. A transaction need not propagate to the whole network in order to be included; for instance, it can reach miners in its continent in 50ms and get mined after 200ms. The frequency also decreases post-inclusion confirmation times due to the increased density of the mining sampling process. Not to say confirmation times decrease tenfold, because they are now dominated by block latency which hasn’t changed. Rather, by back-of-the-envelope calculations, they have improved 30% (for the advanced: the tail of the Poisson governing worst-case DAG width diminishes faster, thus K can be set relatively lower, from 18 (1bps) to 124 (for 10bps) and not to 180 as one might expect).

Block parallelism: block parallelism increases with the block rate, and that, contrary to what you might think, is good. Despite collisions being slightly increased due to block parallelism, parallelism is crucial for creating a more fair system. It means there isn’t a monopoly of a single winning miner per round, but rather blocks must compete and make wise and competitive decisions within the latency round. The implications can be huge and far-reaching.

Oracle systems and MEV kickback auctions are some of the preliminary efforts. Going more into this is out-of-scope. I also need to justify why finance is becoming more relevant post-crescendo… assuming that’s the case, I think that even without implementing MEV kickback designs explicitly in consensus (yet), the mere intra-round “chaos” of the parallel DAG at 10 bps will already make economic manipulation much harder than in other, leader-based systems.

Other changes included in crescendo. How do I start, there’s so much.

KIP-9 is integrated into consensus, baking our unique state bloat solution inherently into the system. By the way, we call this “harmonic” sub-protocol the name STORM (for STORage Mass). In the process, KIP-9 was extended to include UTXO storage plurality (i.e., taxing a UTXO which consumes more storage appropriately), making it more futureproof.

KIP-10 adds support for basic covenants and additive addresses.

KIP-13 regulates transient storage requirements more strictly. Smart contract-related changes: KIP-14 enables payloads, allowing txns to carry arbitrary data (e.g., smart contract function calls).

KIP-15 is a technically minor upgrade — comprising one line of code — but enables a conceptually meaningful feature, allowing nodes to archive only transactions and prove their sequencing and acceptance trustlessly. This is significant for allowing pre-zk era L2 nodes to store and prove full SC execution to new syncers at a reasonable cost—hence effectively making such systems possible right after crescendo. The change proposed is a tiny subset of the zk design proposal (see Kaspa research forum—based rollups design posts) where such a mechanism was proposed as a necessary requirement for zk systems to operate over Kaspa, and turned out to have significant value also pre-zk. Overall, this means that preliminary SC L2s are possible over post-crescendo Kaspa (or Kaspa 2.0 as @hashdag refers to it internally) with sufficient trust models.

Crescendo is an historical moment in permissionless distributed systems, showing that a multi-leader consensus real-world system can achieve block times shorter than global internet round-trip time (RTT) without artificially suppressing the P2P network size or assuming proximity. Link

 

The post Kaspa Updates to Crescendo and 10BPS appeared first on Kaspa.

]]>
53214
Calling all Kaspa integrations to run a Testnet-10 node https://kaspa.org/calling-all-kaspa-integrations-to-run-a-testnet-10-node/ Mon, 17 Mar 2025 13:46:20 +0000 https://kaspa.org/?p=53049 Overview The Kaspa’s 10BPS network has now been running continuously for nearly a year and the Testnet-10 network has been hardforked to 10BPS. The latest release at https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.17.1 contains all […]

The post Calling all Kaspa integrations to run a Testnet-10 node appeared first on Kaspa.

]]>

Overview

The Kaspa’s 10BPS network has now been running continuously for nearly a year and the Testnet-10 network has been hardforked to 10BPS. The latest release at https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.17.1 contains all the optimizations that the team has been working this past year. We believe the optimization state of the node is very close to what it will be on mainnet and so our development will now focus on Enhanced User Experience. This is where you, the pools, the exchanges and other integrators come in. We would like to invite you to run a Testnet-10 node and try your pool/exchange/other software on it to check how your integration behaves in the 10BPS network. We would love to hear from you, the good feedback and any opportunities for improvement.

Getting Started

Updating GRPC proto

Make sure that you get the updated message.proto and rpc.proto from the rusty-kaspa repo at https://github.com/kaspanet/rusty-kaspa/tree/master/rpc/grpc/core/proto

Working with TN10 network requires using the latest proto available.

Notably, a new field mass was added to RpcTransaction. If you use GetBlockTemplate and SubmitBlock you need the updated proto to get the values for the mass field in the transactions inside your block template. Then, when you call SubmitBlock you need to make sure that the mass fields remain set. If you’re a pool, your pool is working if it is able to mine blocks with 2 or more transactions on Testnet-10.

Minimum Recommended Specifications

  • 8-core CPU
  • 16 GB RAM
  • 256 GB SSD
  • 5MB network

If you are using a higher-spec node for your mainnet node, please continue to try that same spec out when trying out this node. If you are using specs lower than the above in mainnet, please use at least the above specs for your 10BPS testing.

Note: These minimum recommended specifications are subject to change as we gather feedback from mainnet node operators about their experience running a 10BPS node.

Using the release

Download the binary from the release at https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.17.1

To run the node on TN10, use:

./kaspad --utxoindex --testnet --netsuffix=10 --disable-upnp --rpclisten=0.0.0.0

If you’re running your software on the same machine as the node, use --rpclisten=127.0.0.1

Compiling from source

You may want to compile the node from source. To do so, follow the instructions at here to setup the dependencies https://github.com/kaspanet/rusty-kaspa?tab=readme-ov-file#installation

And then run your node with:

cargo run --bin kaspad --release -- --utxoindex --testnet --netsuffix=10 --disable-upnp --rpclisten=0.0.0.0

If you’re running your software on the same machine as the node, use --rpclisten=127.0.0.1

Giving Feedback

We would love to hear your experience, the good and the bad. Please let us know by sending a message on the #testnet channel of the Kaspa Discord

The post Calling all Kaspa integrations to run a Testnet-10 node appeared first on Kaspa.

]]>
53049
TN10 – Crescendo Hardfork Node Setup Guide https://kaspa.org/tn10-crescendo-hardfork-node-setup-guide/ Wed, 05 Mar 2025 00:15:12 +0000 https://kaspa.org/?p=52928 The post TN10 – Crescendo Hardfork Node Setup Guide appeared first on Kaspa.

]]>

Kaspa Testnet 10 (TN10) – Crescendo Hardfork Node Setup Guide

Kaspa is about to take a significant leap with the Crescendo Hardfork, as detailed in KIP14, transitioning from 1 to 10 blocks per second. To ensure a stable rollout, Testnet 10 (TN10) will first undergo this shift on approximately March 6, 2025, 18:30 UTC. By running TN10 and providing feedback, you help prepare for a smooth mainnet upgrade, tentatively planned for the end of April or early May.

Important Note:

  • Version 0.17.0 does not support TN11. Some participants should keep TN11 nodes running on the latest stable release or stablebranch until TN10’s performance is proven stable.

Recommended Hardware Specifications

  • Minimum:

    • 8 CPU cores
    • 16 GB RAM
    • 256 GB SSD
    • 5 MB/s (or ~40 Mbit/s) network bandwidth
  • Preferred for Higher Performance:

    • 12–16 CPU cores
    • 32 GB RAM
    • 512 GB SSD
    • Higher network bandwidth for robust peer support

While the minimum specs suffice to sync and maintain a TN10 node with the accelerated 10 bps, increasing CPU cores, RAM, storage, and bandwidth allows your node to serve as a stronger focal point on the network. This leads to faster initial block download (IBD) for peers syncing from your node and provides more leeway for future storage growth and optimization.


1. Install & Run Your TN10 Node

  1. Obtain Kaspa 0.17.0 binaries
    Download and extract the official 0.17.0 release, or build from the master branch by following the instructions in the project README.

  2. Launch the Node
    While TN10 is the default netsuffix, specifying it explicitly is recommended:

    kaspad --testnet --netsuffix=10 --utxoindex
    

    (If running from source code:)

    cargo run --bin kaspad --release -- --testnet --netsuffix=10 --utxoindex
    

Leave this process running. Closing it will stop your node.

  • Advanced Command-Line Options:
    • --rpclisten=0.0.0.0 to listen for RPC connections on all network interfaces (public RPC).
    • --rpclisten-borsh for local borsh RPC access from the kaspa-cli binary.
    • --unsaferpc for allowing P2P peer query and management via RPC (recommended to use only if not exposing RPC publicly).
    • --perf-metrics --loglevel=info,kaspad_lib::daemon=debug,kaspa_mining::monitor=debug for detailed performance logs.
    • --loglevel=kaspa_grpc_server=warn for suppressing most RPC connect/disconnect log reports.
    • --ram-scale=3.0 for increasing cache size threefold (relevant for utilizing large RAM; can be set between 0.1 and 10).

2. Generate Transactions with Rothschild

  1. Create a Wallet
rothschild

This outputs a private key and a public address. Fund your wallet by mining to it or obtaining test coins from other TN10 participants.

  1. Broadcast Transactions
rothschild --private-key <your-private-key> -t=10

Replace with the key from step 1. The -t=10 flag sets your transaction rate to 10 TPS (feel free to try different rates, but keep it below 50 TPS).


3. Mining on TN10

  1. Download the Miner
    Use the latest Kaspa CPU miner release which supports TN10.

  2. Start Mining

kaspa-miner --testnet --mining-address <your-address> -p 16210 -t 1

Replace with your TN10 address (e.g., from Rothschild) if you want to mine and generate transactions simultaneously.


Summary & Next Steps

  • Node Sync:
    kaspad --testnet --netsuffix=10 --utxoindex
  • Transaction Generation:
    rothschild --private-key <your-private-key> -t=10
  • Mining:
    kaspa-miner --testnet --mining-address <your-address> -p 16210 -t 1

By participating in TN10, you help stress-test the Crescendo Hardfork environment and prepare for a robust mainnet upgrade in end of April / early May. Share any challenges or successes in the #testnet Discord channel, and thank you for supporting Kaspa’s continued evolution.

The post TN10 – Crescendo Hardfork Node Setup Guide appeared first on Kaspa.

]]>
52928
Powered by Kaspa https://kaspa.org/powered-by-kaspa/ Thu, 13 Feb 2025 20:18:39 +0000 https://kaspa.org/?p=52537 The post Powered by Kaspa appeared first on Kaspa.

]]>

Introducing Powered by Kaspa
A New Era for Kaspa’s Digital Ledger Technology

By Chad Ballantyne (Rhubarbarian)
Creator of the Kaspa Brand

For over a year, we’ve have been laying the groundwork for a new narrative—one that positions Kaspa as not just a digital currency but as the most advanced Distributed Ledger Technology (DLT) on the planet. With smart contracts around the corner and the upcoming DAG Knight Protocol, we’re taking that vision to the next level with a new brand initiative: Powered by Kaspa!
Although many Kaspa projects are still in different stages of development, we felt it important to cast the vision and get the conversations going under a strong narrative.

 A Secondary Brand to Complement Kaspa Currency

The Kaspa currency brand is here to stay. Kaspa is the fastest, most secure, and fully decentralized currency aiming to run at the speed of the internet. However, there are two sides to the Kaspa coin—one is the groundbreaking currency, and the other is the revolutionary Distributed Ledger Technology (DLT) powering it. Powered by Kaspa is a secondary brand (or tag) that highlights this underlying technology, expanding its reach beyond currency use into industries that require high-speed, scalable, and secure digital ledgers.

The “Powered by Kaspa” Concept

This new branding initiative is designed to highlight Kaspa’s unique use case as a leading DLT for high-speed, scalable, and decentralized applications. The Reverse K from the Kaspa coin brand is a powerful symbol, known world-wide and now, with energy waves emanating from it, it represents Kaspa’s power being released, tapped into, and connecting across industries.

This brand will serve as a recognizable tag for projects built on Kaspa’s technology, from enterprise solutions to decentralized applications, inside Crypoland and out in the real world. It will be a stamp of trust and innovation, much like how certain industry leaders have successfully branded their core technologies to show their impact (think: “Intel Inside”).

This is not meant to be seen as large and flashy, rather subtly placed to not take away from any projects core visual brand.  It could be used more in the early stages of the project launch and less as your project grows.  Like any great tech, it’s better to work great and not be “seen.”

Real-World Applications: DePIN, RWA, and Enterprise Use Cases

The Powered by Kaspa initiative will be especially relevant in key areas, including:

– Decentralized Physical Infrastructure Networks (DePIN) – Projects that leverage Kaspa’s ultra-fast and scalable DLT for decentralized infrastructure, including IoT networks, decentralized storage, and computational resource sharing.

– Real-World Asset (RWA) Tokenization – By providing a secure and scalable ledger, Kaspa enables the seamless tokenization of assets such as real estate, commodities, and financial instruments, unlocking liquidity and efficiency in global markets.

– A New Banking Standard (Warpcore by Kii) – A next-generation financial framework leveraging Kaspa’s speed and security to create an open and decentralized banking infrastructure.

– Stablecoins for Everyday and Energy Sector Use (Gigawatt Stable Coin by Kii) – Enabling stable digital assets not just for transactions but also for balancing energy markets and payments in decentralized grids.

– Insurance, Agriculture, Logistics, ETFs, and More – As highlighted by the KII project, industries such as insurance, agricultural trade, supply chain logistics, and exchange-traded funds (ETFs) will benefit from Kaspa’s transparent and immutable ledger.

Classic Crypto Ecosystem
The Powered by Kaspa  brand will also be an essential part of the growing classic crypto ecosystem, which includes developer-driven initiatives specifically in the cryptocurrency space. These groups like KEF, Kasplex and others are leading the charge in building out essential applications for:

  • Classic Tokens & Meme Coins – A vibrant and innovative playground for community-driven assets leveraging Kaspa’s DLT.
  • NFT Marketplaces & Applications – Providing ultra-fast and secure NFT transactions with Kaspa’s parallel block processing.
  • Kaspa-Tech-Centered Exchanges – Decentralized and centralized exchanges that will benefit from the security, finality, and speed of Kaspa’s infrastructure.

We hope these initiatives will thrive under the Powered by Kaspa banner, ensuring that every application built on Kaspa’s technology has a clear, unified brand identity to showcase its connection to this groundbreaking technology.  It can be applied to images, videos and/or just used in articles and descriptions.

With initiatives like Kaspa Industrial Initiative (KII) and Kaspa Ecosystem Foundation (KEF) (and many more to come), committed to enlarging the ecosystem, Powered by Kaspa will be a unifying brand for businesses, developers, and communities utilizing Kaspa’s DLT.

Empowering People | Powering the Planet

As we roll out the Powered by Kaspa brand, we’ll provide a comprehensive brand standards guide and resource package to help projects integrate the branding seamlessly. Whether you’re a developer launching a Token, an enterprise building on Kaspa, or a community initiative leveraging the technology, this brand is yours to use.

Kaspa has always been about empowering people through digital currency with its eye on powering the planet with decentralized innovation. We see Powered by Kaspa as the next evolution of that mission.

Stay tuned for the official brand standards guide, examples, and resources. It’s time to show the world what’s possible when technology is truly Powered by Kaspa.

NOTE:  This is not a meant to be a mandatory use brand.  As we are all part of a DAO, we leave it up to the individual projects to tap into this narrative and visual brand.  Although we do recommend it!  If you are invested in how you could use it, contact the Rhubarbarian in TG or Discord and he and his crew will be happy to guide you in it’s use for your particular project.

 

Powered by Kaspa (PBK) Criteria Checklist

Who Can Use the “Powered by Kaspa” Brand?

The “Powered by Kaspa” (PBK) brand is designed for applications, tools, and technologies that are built on or directly utilize Kaspa’s Distributed Ledger Technology (DLT). It is primarily intended for real-world enterprise applications that leverage Kaspa’s speed, scalability, and security.

The “Powered by Kaspa” brand is reserved for applications and tools where Kaspa DLT is an essential component of the technology itself. If your project runs on Kaspa DLT, with Kaspa DLT under the hood, and contributes to real-world or enterprise solutions, it qualifies. If your project simply accepts Kaspa or interacts with it superficially, it does not qualify.

Branding guidelines are below.

What Would Be Considered
“Built On” Kaspa?

A project would be truly “built on” Kaspa if it:

✅  Operates directly within Kaspa’s DLT framework – e.g., a dApp that leverages Kaspa’s ledger to store and execute logic.

✅  Extends Kaspa’s protocol – such as a smart contract layer, DeFi protocol, or an L2 that interacts natively with the GHOSTDAG structure.

✅  Utilizes Kaspa for core execution, validation, or consensus rather than just using it for transactions.

PBK Qualification Criteria

To qualify for the “Powered by Kaspa” brand, a project must meet the following criteria:

*Built on or integrates Kaspa DLT – The application or technology must actively use Kaspa’s digital ledger under the hood.

Enables real-world use cases – Primarily designed for enterprise markets, industries, or decentralized infrastructure (e.g., DePIN, RWA, finance, supply chain, energy, etc.).

Enhances the Kaspa ecosystem – Contributes to the growth and adoption of Kaspa technology through innovation and implementation.

Adheres to Kaspa’s decentralization ethos – Aligns with Kaspa’s core principles of open-source, decentralized, and permissionless innovation.

Adds technical or functional value – Uses Kaspa’s DLT for a unique function beyond just token transactions.

Exclusions – Who Should Use “Powered by Kaspa”?

🚫 Exchanges, Wallets, or Payment Processors – Platforms that list or accept Kaspa but do not integrate Kaspa’s DLT as part of their core technology.

🚫 Marketing or Awareness Projects – Initiatives that promote Kaspa but do not develop apps, tools, or services utilizing the DLT.

🚫 Non-Kaspa Blockchain Projects – Apps that do not natively use Kaspa’s DLT but merely reference Kaspa in some way.

New Kaspa Terms

Kaspafy (verb)
/ˈkæs-pə-fī/

Definition:

1. To enhance, optimize, or revolutionize a system, technology, or industry by leveraging Kaspa’s ultra-fast, decentralized, and scalable blockDAG infrastructure.

2. To remove inefficiencies, centralization, and bottlenecks by adopting a network Powered by Kaspa.

3. To future-proof digital finance, enterprise markets, and decentralized applications (dApps) with Kaspa’s blockDAG architecture.

Sample Uses:

“The company decided to Kaspafy their payment system, making transactions instant and fee-efficient.”

“We need to Kaspafy our supply chain to improve transparency and traceability.”

“By adopting Kaspa’s infrastructure, they were able to Kaspafy their cross-border remittance services.”

Kaspafied (adjective)
/ˈkæs-pə-fīd/

Definition:

  1. Enhanced, upgraded, or transformed through Kaspa’s digital ledger technology.
  2. Fully integrated with or utilizing Kaspa’s blockchain for speed, scalability, and decentralization.

Sample Uses:

“The logistics network is now Kaspafied, ensuring real-time tracking and settlement.”

“A Kaspafied gaming platform allows players to own and trade digital assets securely.”

“Once their finance infrastructure was Kaspafied, transactions became seamless and near-instant.”

Kaspafication (noun)
/ˈkæs-pə-fɪ-ˈkeɪ-ʃən/

Definition:

  1. The process of integrating or optimizing a system, service, or industry using Kaspa’s blockchain technology.
  2. The shift towards a decentralized, high-speed, and scalable infrastructure powered by Kaspa.

Sample Uses:

“The Kaspafication of the global remittance industry could eliminate delays and high fees.”

“With ongoing Kaspafication, businesses are experiencing a new level of efficiency and security.”

“The company’s Kaspafication strategy involved migrating legacy databases onto Kaspa’s blockchain for better performance.”

Sample Uses
Click to enlarge

The post Powered by Kaspa appeared first on Kaspa.

]]>
52537
Crypto’XR 2025: A Breakthrough Event for Kaspa France https://kaspa.org/cryptoxr-2025-a-breakthrough-event-for-kaspa-france/ Sun, 09 Feb 2025 15:45:56 +0000 https://kaspa.org/?p=52601 The post Crypto’XR 2025: A Breakthrough Event for Kaspa France appeared first on Kaspa.

]]>

Crypto’XR 2025: A Breakthrough Event for Kaspa France

Presence & Organization
Crypto’XR 2025 was a milestone event for the Kaspa France team, marking a significant step forward in our efforts to expand Kaspa’s visibility and adoption in the crypto ecosystem. Our stand was strategically placed in the “Mining” space, reinforcing Kaspa’s strong Proof-of-Work (PoW) identity. Positioned near Blobb.io, this location naturally attracted miners and blockchain enthusiasts, sparking insightful discussions on the future of mining and Kaspa’s place in it.
The Kaspa France delegation consisted of four dedicated ambassadors, along with Eliott Mea, JC, and Mourad. Throughout the two-day event, we engaged with approximately 500 attendees, experiencing an uninterrupted flow of visitors. Every interaction further refined our ability to present Kaspa compellingly, fostering greater enthusiasm within our team.

One of the key highlights was our exchange with “For Mining Space,” where we explored potential collaborations in the mining sector. These discussions reinforced the growing recognition of Kaspa as a serious player in the blockchain space.

Visibility & Content
Our presence at Crypto’XR was amplified by engaging content and interactive sessions:
Live Stream: A dynamic session featuring Marwane & JC, attracting around 70 live viewers on YouTube. The feedback was overwhelmingly positive, with many appreciating our insights into Kaspa’s unique architecture.

Workshop on Stage: One of the defining moments of the event was the workshop co-hosted by Eliott Mea, who had previously conducted his final internship under Yonatan Sompolinsky. The session delved into the robustness of Kaspa’s Whitepaper and BlockDAG architecture, drawing considerable attention from both seasoned crypto experts and newcomers. A high-quality video recording of this session is expected to be released soon, further amplifying its impact. During the workshop, we answered questions in a decentralized manner, embodying the very spirit of Kaspa and demonstrating this philosophy to a broad audience.

Encounters & Business Opportunities
The event provided fertile ground for meaningful business discussions and strategic connections:
Developers & Entrepreneurs: We sensed strong anticipation for Layer 2 solutions and smart contracts, indicating a clear demand for Kaspa’s upcoming developments.

Crypto Payments: Companies like Braille and Kamea showed keen interest in integrating Kaspa into their payment infrastructures, a testament to its growing credibility as a transactional cryptocurrency.
Exchanges & Listings: Productive discussions with SwissBorg opened the door to potential exchange listings, a crucial step toward greater market adoption.
Influencers & Media: We secured opportunities for interviews with key French crypto influencers, enhancing Kaspa’s media presence.
Blockchain Education: Engaging discussions with Alyra, a leading blockchain school, paved the way for a future presentation on Kaspa, expanding its reach in the educational sector.
Bitcoin Maximalists: Some of our most intense yet rewarding conversations were with BTC maximalists. We noted a shift in their perspective, with many acknowledging Kaspa’s merits and admitting to mining KAS themselves—without ever selling it. This revelation underscored the respect Kaspa is earning, even among the most hardened Bitcoin advocates.

Engagement & Emotional Impact
Crypto’XR was not just about visibility; it was about unity, energy, and validation. Our stand remained constantly occupied, reflecting a tangible curiosity and excitement around Kaspa. Many visitors already knew about Kaspa, while others left intrigued by its potential. The diversity of ambassador profiles allowed us to provide tailored and complementary answers to different audience segments, reinforcing our collective strength.

One of the most exhilarating aspects was the intellectual challenge presented by skeptics. Engaging in deep technical discussions, dismantling doubts, and sparking curiosity left us with a strong sense of accomplishment. These moments of rigorous debate and genuine interest reaffirmed that Kaspa is on the right trajectory.

Moreover, the camaraderie among the Kaspa France team was palpable. The experience of representing Kaspa together, exchanging knowledge, and witnessing the ecosystem’s expansion firsthand was incredibly fulfilling. It strengthened our conviction that we are not just promoting a blockchain but a movement built on transparency, efficiency, and decentralization.

Next Steps & ROI
The momentum gained at Crypto’XR must now be leveraged to drive Kaspa’s adoption further:

  • Capitalizing on newly established contacts to accelerate ecosystem development.
  • Structuring an ambassador recruitment program in France to maintain our growth trajectory.
  • Strengthening our presence at major upcoming events, particularly PBW (Paris), ETHcc (Cannes), and Surfin’Bitcoin (Biarritz).

Conclusion
Crypto’XR 2025 validated our efforts, expanded our network, and strengthened Kaspa’s foothold in the French crypto landscape.

Thanks to the support of Kaspa Ecosystem Foundation (KEF), we were able to create a meaningful impact, engage with key stakeholders, and solidify our presence in the industry.

Thanks to the Rhubarbarians and the Community Marketing Fund for supporting us all with promotion, planning and design for the merch, banners and stand designs and presentational materials.

The journey is far from over, but Crypto’XR has set the stage for what’s to come: greater awareness, stronger collaborations, and the unstoppable rise of Kaspa.

The post Crypto’XR 2025: A Breakthrough Event for Kaspa France appeared first on Kaspa.

]]>
52601
Kaspa Meetup Istanbul, Türkiye https://kaspa.org/kaspa-meetup-istanbul-turkiye/ Thu, 06 Feb 2025 20:51:43 +0000 https://kaspa.org/?p=52549 The post Kaspa Meetup Istanbul, Türkiye appeared first on Kaspa.

]]>

Kaspa Istanbul Meetup
Istanbul, Türkiye
January 24, 2024
7:00 PM – 10:00 PM (GMT+3)

On January 24, 2024, at the Avantgarde Urban Levent Hotel, in the heart of Istanbul, the Kaspa Istanbul Meetup brought together crypto enthusiasts, miners, and investors from across Türkiye. With attendees from cities like Çanakkale, Yalova, Denizli, Zonguldak, and Ankara, the event welcomed around 50 participants, creating a vibrant and engaging atmosphere.

A Diverse Community, A Shared Passion
The meetup attracted a diverse group of professionals, including students, crypto professionals, businesspeople, graphic designers, government officials, engineers, and many more. Despite their varied backgrounds, everyone shared a common passion: Kaspa and the future of crypto.

Kaspa’s Presence and Networking Opportunities
The three-hour-long event was filled with insightful conversations and valuable networking opportunities. Additionally, three representatives from local exchanges attended, providing a unique chance to introduce them to Kaspa and its potential in the Turkish crypto landscape.
The discussions extended beyond the main gathering, as participants continued their conversations in smaller groups, forming meaningful connections.

Fortune Cookies & Kaspa Merchs
Upon arrival, attendees received Kaspa-branded t-shirts and merchandise from Rhubarb Media and funding from the CMF, fostering a sense of unity within the community.
One of the most exciting moments of the night was the Kaspa fortune cookie giveaway! Each cookie contained messages highlighting Kaspa’s unique features, while a few lucky participants won up to 500 $KAS rewards, adding an extra layer of excitement to the event.

Additionally, guests enjoyed a delightful selection of hot and cold snacks and delicious desserts, making the evening even more enjoyable.

A Huge Thanks to the Kaspa Community!  
This meetup was made possible thanks to the generous donations and support from the Kaspa community. A big shoutout to everyone who contributed, attended, and helped organize such a successful event!
The Kaspa community continues to grow and thrive with its engaging and inclusive spirit. We look forward to seeing even more of you at our future events!

We would also like to take this moment to remember those who tragically lost their lives in the recent Bolu fire and express our heartfelt condolences to their families and loved ones.

~ Esma

 

The post Kaspa Meetup Istanbul, Türkiye appeared first on Kaspa.

]]>
52549
Stable Release v0.16.0 is out! https://kaspa.org/stable-release-v0-16-0-is-out/ Wed, 29 Jan 2025 19:31:53 +0000 https://kaspa.org/?p=52525 Stable Release version v0.16.0 is now available at https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.16.0 This release contains several optimizations that are expected to significantly improve performance and reduce CPU, storage and RAM consumption for mainnet […]

The post Stable Release v0.16.0 is out! appeared first on Kaspa.

]]>
Stable Release version v0.16.0 is now available at https://github.com/kaspanet/rusty-kaspa/releases/tag/v0.16.0

This release contains several optimizations that are expected to significantly improve performance and reduce CPU, storage and RAM consumption for mainnet node operators.

Some of the optimizations included are:

  • Parallel Muhash
  • Parallel transaction input processing
  • Optimized header validation, reducing storage footprint which affects pruning as well

Initial Block Download (IBD) times have been observed to complete in as low as 15 minutes with these changes in place.

Important Note for Mainnet Node Operators

This is the first stable release that includes the database version upgrade introduced in #494. When you run this version with an existing datadir, you may be asked to upgrade your database version in CLI. To proceed, type y or yes and hit enter. Alternatively, you can run this version with a –yes flag to skip the interactive question.

This database upgrade is a one-way path, which means after updating your datadir to the new version, you won’t be able to go back to an earlier version.

It is strongly recommended that you upgrade to this version at your earliest convenience and definitely before the Crescendo hardfork version.



The post Stable Release v0.16.0 is out! appeared first on Kaspa.

]]>
52525