twitter.com

twitter.com

twitter.com

everyone KIP14 — The Crescendo Hardfork, the exact spec and design of the upcoming Crescendo is out for public review and discussion

github.com

Hello @everyone. I’m grateful to the moderators for the one-time opportunity to present our project to the community. My name is Pavel, and my team is working on Igra Network, an EVM-compatible programmable layer (L2) on Kaspa L1, with fast probabilistic finality and support for 3000 TPS or more. We aim to be the first based ZK rollup on Kaspa. Our short-term goal is to bring programmability to Kaspa by deploying a reliable, battle-tested EVM on Kaspa’s secure PoW DAG system, initially using Kaspa L1 as a sequencer without a ZK bridge (yet). Long-term, we aim to establish based ZK rollups as a standard for L2s and Kaspa as the leading decentralized sequencer and the industry standard for programmable PoW, surpassing all similar L2 solutions. We're sharing Kaspa’s L2 vision of based ZK rollups and atomic composability, as described in <@&1009432608318443550> ’s post (https://research.kas.pa/t/atomic-composability-and-other-considerations-for-l1-l2-support/193). This also applies to the principle of account abstraction (see

x.com

We believe that a fully compatible EVM on Kaspa and access to existing Ethereum tools can spur adoption, attract builders to launch applications, and unlock liquidity through myriad new business cases. Our team combines blockchain industry veterans and DAGLabs alumni. We're consulting with Kaspa core to align our roadmap and vision. We plan to launch a testnet by the end of Q1 2025 and mainnet a few months later. In the next couple of weeks, we'll publish a series of posts to share our vision and would love to hear back from the Kaspa community! I’d also greatly appreciate your help in sharing this message. Our website: https://igralabs.com/, X:

x.com

and Linkedin:

linkedin.com

x.com

CMF is on empty. So thanks for any support - comments on X post help as well. Been a privilege to serve these past 2.5 years!! Link to news blog -

kaspa.org

Link to Tweet -

x.com

In the interest of transparency and knowledge-sharing, Kaspa core research and development discussions (previously private) will now be made public in a view-only Telegram group (at

t.me

). This supplements the discussions already occurring in the Discord’s #research and #development channels. We would like to invite developers, enthusiasts and the curious to join the new TG group and learn more about the development process and the various topics discussed. This initiative provides transparency to the broader community and a chance for new researchers and developers to closely follow and study the discussions. If you want to express your thoughts on a discussed topic, please use the general TG group or the various Discord channels

twitter.com

x.com

x.com

A quick explanation: global block ordering in Kaspa is started by searching for a k-cluster (=computing a GhostDAG): a set of all blocks in Kaspa's history such that from each one you can draw a link arrow (either direct or indirect, via parents and their parent, or children and their children) to almost each one, in the past or the future; and there are never more than k blocks in the cluster for any given one in it that you cannot reach from that given one. For the purposes of reliable and secure pruning of outdated data, exactly the same k-cluster must be separately built for all blocks whose difficulty is 2+ times higher than the threshold difficulty at the time of each such block's appearance; another one for 4+ times higher diff blocks, one more for 8+ times higher, and so on, potentially up to blocks with 2^255 times higher difficulty than the given threshold at that time. This is called a higher-level Ghostdag entries computing. Previously, this operation was performed for each newly found block, although it was not directly necessary at each moment — but it was easier to implement. Now, thanks to @coderofstuff, these calculations are performed only when necessary: ​​for example, before performing a pruning. This is another in a long series of optimizations that will allow a Kaspa node to be run on inexpensive hardware, and will allow Kaspa to remain a truly decentralized L1 solution even after the transition to 10 blocks per second — unlike many widely hyped "cryptocurrencies" that, in their undoubtedly quite fast operation, still rely on a narrow circle of extremely powerful, tightly coupled servers that are unaffordable to the vast majority of the world's population. Cont'd:

t.me

twitter.com

twitter.com

x.com

twitter.com

x.com

Important note for the users of the 3rd-party wallet KASWARE: If you are currently minting KRC-20 tokens, please look at my announcement on the ⁠development channel

discord.com

please help spread the news. ask everyone to update their kasware wallet to the latest 0.6.38.3. and we have added high fee warning. tutorial to update manually. 所有人请升级你的kasware钱包到最新版0.6.38.3. 这会使你的交易费用降低，减少恶意竞争。

docs.kasware.xyz

Kaspa NG v0.3.0-rc1 (release candidate 1) has been released and can be downloaded from

github.com

or built from the master branch at

github.com

This version includes the recently released Rusty Kaspa 0.15.1 as well as a variety of updates and features (please read release notes for more information). The web version of Kaspa-NG available at

kaspa-ng.org

has also been updated to this v0.3.0-rc1 release. (note that if you have used the web version in the past, you may need to reset your browser cache by hitting Ctrl+Shift+R or Cmd+Shift+R on MacOS). Note that if you are using Windows, you might require an update to x64 Visual C++ Redistributables 14.40.33810.0 in order to run Kaspa NG. If you have any questions or need help, please join the <#1199819135404740749> channel.

x.com

x.com

x.com

x.com

Please check out the AFT thread if your interested in attending the AFT conference.

discord.com

fxtwitter.com

x.com

Ledger Live Integration funding pool ---------------------- We've launched a fundraising campaign to collect the necessary funds for implementing Kaspa support in Ledger Live. Thе donation address belonging to the Kaspa Public Dev Fund wallet, controlled by the Treasurers, is: kaspa:pzhefv7sz6g8tsygcelkyg9jyky4gkp9m9ugpvf5lt6scjuky27fz6qy0e5rw Link to explorer The implementation is realized by @lamer11010 and the funds will be transferred after Kaspa is fully integrated in Ledger Live. Thank you! KAS balance: 104,693 KAS of needed 200,000 KAS 52.35% done. 🟩🟩🟩🟩⬜⬜⬜⬜

Alright, let me give you a brief on what's happening as I understand it. - The Kaspa network is running smoothly and in accordance with its designed logic. - The Kasplex indexer seems to be running without any hitches, too. - Despite this, there are issues both with minting KRC-20 tokens and with ordinary user transactions. This can be attributed to the following combination of factors: First off, the devs at Kasware (the wallet) didn’t quite nail their solution for minting, both in terms of software and logistics. The most glaring issue is their servers are overloaded. For some reason, instead of just broadcasting a prepared transaction through a node into the network, their wallet first makes a call to the Kasware server. This could be related to an additional fee for minting, set at 0.1 Kaspa as stated in the wallet. Secondly - due to the fact that dust attack prevention mechanism is in place on Rust nodes following KIP-9 - when minting transactions are formed, they should have been not just 0.2 Kaspa in size, but ideally at least 1 Kaspa (or their construction logic should have been more complex, taking into account the balance of inputs and outputs) - after all, that transfer still goes to the person’s own wallet, not to someone else's. This would have reduced the impact of the dust attack prevention mechanism, which currently leads to minting transactions having a large weight, close to the maximum allowed. As a result, only about 20 to 40 such transactions fit in a block. With a 1 Kaspa output size, many more could fit. But devs were probably racing against a deadline and didn’t thoroughly check their solution. These problems weren’t visible in the testnet, because there, with 10 blocks per second and very few minters, it looked fine. (Note: pay attention to the difference in approaches between the core developers and third-party developers. Kaspa developers aren’t ever in a rush with releases because they fully understand the consequences of any mistakes. Other developers might potentially afford to loosen these restrictions, but then we might end up seeing what we're observing now). Thirdly, because these transactions are heavy in weight and only about 40 of them fit into a block, a massive backlog has accumulated in the mempool (peaking at around 37,000 transactions, with just under 12,000 at the time of writing). And all these transactions come with high fees. This is why regular users are experiencing problems: their low-fee transactions stand little to no chance of being included in a block, especially compared to minting transactions, since the chance of inclusion is proportional to the fee (more precisely, to the fee/mass ratio, but this interesting aspect is not of much importance in this particular case). And the situation is further worsened by the fact that the ecosystem (sp. wallets and exchanges) are not ready to give their user the ability to effectively compete in the suddenly emerging fee market. Simply put, they lack both the way to inform the user of the current fee size in the network, and to allow them to specify what fee to set. In the end, it looks like the network is dead to regular users, and those trying to mint are also struggling. Successful mints are a matter of luck in getting serviced by the overloaded Kasware servers, and then to be chosen out of thousands of competitors to be included in a block. And probably, those who managed to create their own utility for forming KRC-20-compatible transactions made a smart move. P.S. I want to add that turning off dust attack protection isn't a wise move: the issues for both minters and ordinary users stem from a frenzied demand for transactions, greatly exceeding the network's standard usage intensity. But this will eventually subside because it's an expensive endeavor: currently, each block brings miners an extra $3.5 on top of the regular block reward. However, the consequences of a potential dust attack would remain in the Kaspa network forever, affecting its operation for the duration of its existence. The stakes are incomparable.

Per Ori in Discord: The launch of the Kasplex open beta caused a spike in legitimate network usage, resulting in a natural load -- an increase in confirmation times for all users. The network itself -- P2P, and especially consensus and mining -- has been and is functioning securely as usual and continues to secure transactions and funds. Some community-built explorers couldn't handle the full throughput supported by the network and lagged behind. The latter is ofc a frontend issue and does not affect the network's security or consensus. As with any period of unusual load, fees determine priority: users with urgent transactions can raise their fees and enjoy normal, fast operation. We are talking with the Kasplex team to see how to reduce the load in terms of mass cost with modifications to their wallet. It appears that one of the wallets that is used to mint KRC20 transactions is unnecessarily bloating the transaction mass. We expect this to be temporary, and get fixed once the kasplex wallet fixes the way it builds KRC20 transactions.

If you face a connection issue on KasWare wallet (Connecting network), follow these instructions: Settings > Netowrk > Mainnet Settings > copy and paste the following url: wss://eu-1.kaspa-ng.io/mainnet

Reminder: The Ledger Live crowdfund is still active. Even if you don't use Ledger, many Bitcoiners do. By contributing to crowdfunds like this, you're helping to create a safe, familiar, and easy-to-use platform for the BTC maxis. They typically aren't fans of due diligence and rely on brands and influencers. Witnessing Kaspa's undeniable dominance everywhere, they look should hopefully encourage them to learn and adopt Kaspa. If they like BTC so much, they'll love Kaspa.

explorer.kaspa.org

discord.com

The monthly Discord R&D meeting for July has been rescheduled for July 9th,14:00 UTC This meeting will be with hashdag and the topic will revolve around the future and development of smart contracts. The start time for this meeting is approximate and if delayed, I'll try my best to keep everyone updated. Thanks

x.com

In accordance with the proposal accepted here https://discord.com/channels/599153230659846165/935851925608472617/1253613020085616711, we launch a fundraising campaign to collect the necessary funds for implementing Kaspa support in Ledger Live. Thе donation address belonging to the Kaspa Public Dev Fund wallet, controlled by the Treasurers, is: kaspa:pzhefv7sz6g8tsygcelkyg9jyky4gkp9m9ugpvf5lt6scjuky27fz6qy0e5rw https://explorer.kaspa.org/addresses/kaspa:pzhefv7sz6g8tsygcelkyg9jyky4gkp9m9ugpvf5lt6scjuky27fz6qy0e5rw?page=1, live progress:

kas.live

Collection goal: 200 000 Kas. Deadline: would be nice to fill it in 2 weeks (by 2024 July 06), but let's start the experiment here and not close the fundraiser until either the goal is reached, or the integration is completed. The funds raised will, as usual, be paid to the implementer, @lAmeR11010, after the integration with Ledger is complete, i.e., after any Ledger owner can operate Kaspa through Ledger Live. I hope many Kasparians will participate, especially those who would like to see Kaspa in Ledger Live. A small donation from each of you - and you will feel your Kaspa even more secure. It is definitely worth it! ORIGIN:

discord.com

www.youtube.com

A routine R&D meeting has been scheduled for the first Wednesday of every month on Discord. This is a relaxed and informal meeting that will allow showcasing the latest R&D news, answer questions, and discuss upcoming developments. The sessions can be freeform, agenda-focused, or even just open brainstorming sessions, open to public engagement or closed. We can adjust this for the topics and interests of the participants. By having a regular schedule, we remove the challenge of organizing a bunch of devs, conflicting schedules, and making last-minute announcements and changes. This way, there is always next month. Participation is voluntary. You can find the event at the top of the Discord app in the calendar to check dates and set reminders.

I'd like to also draw miners' attention here, there's currently a strong bias towards the f2 pool on Kaspа. Not anything critical, but looks unpleasant from the mining powers centralization standpoint. So would you please consider switching your ASICs to any other pool of your preference, to spread the power and support decentralization of Kaspa mining. Please note that, unlike traditional, slower cryptos, Kaspa's 1 block per second allows for even the smallest pools to be able to find dozens of blocks per day, which is guaranteed to provide you with at least daily payouts, or even several times a day, depending on your personal hashing power. Therefore, do not limit your choice of options to only larger pools. Consider all possibilities. Perhaps some of the small pools will turn out to be especially attractive due to their combination of properties.

Due to the overwhelming success of this crowdfunding campaign, supertypo has decided to close it since the full timeframe isn't needed. Thank you all for your incredible support and contributions!

A crowdfund has launched to cover costs of server and storage rental for hosting wallet.kaspanet.io, api.kaspa.org (backing explorer.kaspa.org), and the historical Kaspa block/transaction database. The API averages ~100 requests per second, and the web wallet maintains about 1500 open sessions. This funding will also support the ongoing maintenance of DNS seeders (mainnet, testnet), public nodes backing central infrastructure, and hosting tools like nodes.kaspa.ws. Your support is crucial for the stability and availability of these critical services! Objective: Cover at least 6 months of infrastructure costs. Amount: Minimum of 20,000 $KAS - Overfunding will be used to extend time of infrastructure services. ETA: ~Two Weeks Donation Address kaspa:qqg68rk7sh3l4pvh4hagz3g84kc2rjdn3f0cz48u7l0epkv73yafu9ln385n8

explorer.kaspa.org

x.com

www.youtube.com

youtu.be

Guys plz join kasplex telegram for any memecoins talk

t.me

twitter.com

Hello, everyone! It's been almost 7 months since we last called on the community's strength to replenish the Kaspa Community Marketing Fund. During this time, the money collected by the community has been used to do a lot of work: more than 1000 designs have been created for various needs, dozens of videos have been produced, KASPA ambassadors have held numerous meetings in their countries, and so much more. You can learn more details about what was done in this document:

docs.google.com

However, the fund, which was already stretched further than initially expected, is, unfortunately, depleted as of today. It's time to conduct another round of collections so that the power of the KASPA enthusiasts in promoting it does not decrease. You can see the details of the planned expenses for the next period in the same document, at the link above. And here is a summary of the request: Objective: top up the CMF for the following 3-6 months. Amount: 91 956 KAS. ETA: no time limit, yet again, the sooner the better 🙂 Donation address: kaspa:qr4s0zf3rxj0uzzzpjr44z7gly0xv3p8qtjfzkre36yq79x05xyvzlmmsjtne

explorer.kaspa.org

(the new address is created this time too, to allow for campaign fundraising visualizer). Let's lay the groundwork for further successes of the community in promoting KASPA! ORIGIN:

discord.com

Hello community 🚨🚨🚨 This weekend Kaspa will be attending Hong Kong WEB3 FESTIVAL 🎉🎉🎉

www.web3festival.org

🗓️ April 6-9, 2024 Shai, @DrBlirpblorp will be speaking along with some global Ambassadors working the Kaspa Booth (B03). Chad, @Rhubarbarian (Canada) Luke, @elldeeone (Australia) Julien, @judaubert (France). For those attending we have a Discount Code (WANXIANG) For an extra 12% off the ticket price We're also planning a big Kaspa meetup

lu.ma

Thanks to Kaspa Ecosystem Foundation for sponsoring this event!

Would like to borrow exactly 1 minute of the communities time. Please take a moment to watch this video.

twitter.com

medium.com

discord.gg

kaspafunding.com

iceriver.io

I compiled a list of questions from X/Twitter and Discord. Please review for completeness.

discord.com

Hello everyone! The other day, having properly voted for it https://discord.com/channels/599153230659846165/935851925608472617/1215381969307963402, we withdrew 176 000 $KAS from the Kaspa public development fund to sponsor the Science of Blockchain Conference 2024 (SBC'24) at Columbia University, New York City, and then market sold them at MEXC for a total of 25 500 USDT (it should be noted that we timed it well because the exchange rate has dropped a bit since then 🙃). We came up with this approach because time was critical, the number of sponsorship slots was limited, and we had to act fast. In doing so, we agreed to compensate for the funds withdrawn by performing a "reverse collection". Now that Kaspa's place as a platinum sponsor of the conference is secured (https://discord.com/channels/599153230659846165/1066838182932525066/1219597778766925904), it is time to focus on this compensation. On this occasion, I am announcing a fundraiser to compensate for the funds withdrawn from the development fund to sponsor the conference. Address: a new one on Kaspa dev fund wallet controlled by the treasures - kaspa:ppnx8w08jc45xnunkgvktzp5lw2du3qrqr9j5yjrx7pf8a8dzstkyfmlsr734 (see the balance

explorer.kaspa.org

Goal: 176 000 $KAS ETA: 2 weeks I ask everyone to participate to the extent that you can afford, as we will surely need these funds: there is plenty of work needed for Kaspa, and it will only increase over time!