https://twitter.com/MichaelSuttonIL/status/1558901387282595843?t=A-Gu2A45CmBM9Gx3ldC4_w&s=19

Guys, new Kaspa Mining Pool https://kaspa-pool.org Try this

Please join us for a Kaspa Community Call. Goals of this meeting are to better organize our community, prioritize marketing initiatives, tap into our community's talents and experiences, and share ideas on how we can maximize the success of our Kaspa ecosystem. Topic: Kaspa Community Call (Community Organization) Time: Aug 12, 2022 08:00 AM Pacific Time (US and Canada), 11:00 PM China Standard Time (China), 04:00 PM British Summer Time (London), 06:00 PM Israel Daylight Time (Tel Aviv) Join Zoom Meeting https://us05web.zoom.us/j/88554576474?pwd=a1d0bkRXVlhzK21IOXRoT1lrUmx3UT09 Meeting ID: 885 5457 6474 Passcode: 4uFE9w

supertypo — Today at 4:57 AM We have made some changes to the wallet server which hopefully will make it better handle the high load. It's back up now. Nginx tuning, the connection pool was exhausted. Also increased per user file system limits in the os to allow for a larger connection pool.

https://twitter.com/moonshotjosh/status/1552830517942358017?s=21&t=Bxqf86wml2G1Nd2l8rq3EQ

IMPORTANT: the vote started !!!! please join Discord and vote!!!!

please take a look to @hashdag point of view about the recent Rust refactoring proposal proposed by @missutton : https://hashdag.medium.com/kaspa-where-to-part-i-ce6a1a2c8eb0

Update from discord : @everyone Hello Kaspers! I'm happy to announce the final funding pool amount of 12 Million KAS. Thanks to everyone who contributed to this pool. Donating funds in such a difficult market situation is not easy and this definitely shows the strength of this community. Hoo.com is currently scheduling the integration process and will get back to us shortly. We'll let you know once the funds have been sent out and of course we'll keep you posted about the integration process in the funding-pools-discussion channel. The listing will be announced through all official channels.

guys, please vote on discord!

Something new is coming... x2! Stay tuned. #branding #exchanges #BlockDag #PoW

@everyone Kaspad v0.12.0 is out: https://github.com/kaspanet/kaspad/releases/tag/v0.12.0 This upgrade is mandatory. It contains a hard fork at DAA score 14687583 (estimated to be on 28/04 16:38 UTC). Everyone who doesn't upgrade will be split off the network. The main focus of the hard fork is to address the issue of deep side chains that spam the network. After the hard fork is activated such side chains will be ignored unless they win the block race and have more blue work than the rest of the network. The hard fork also removes the previous limit on transactions to send less than 21M KAS. Note: whoever who's upgrading directly from v0.11.14 might experience a very long DB migration process, so in that case I would recommend to just delete the old data directory and resync from scratch. P.S. We contacted @aspect and he said that a new corresponding KDX version will be released in the next two days.

Kaspad v0.11.17 is out https://github.com/kaspanet/kaspad/releases/tag/v0.11.17 It fixes a bug that made mining pretty impossible when the mempool is full (it's what caused the mining freeze yesterday). The upgrade is immediate and doesn't require any migration GitHub Release Kaspad v0.11.17 · kaspanet/kaspad What's Changed Decrement estimatedHeaderUpperBound from mempool's MaxBlockMass by @someone235 in #2009 Full Changelog: v0.11.16...v0.11.17

Guys! Please notice that there is scammer that uses Guy Corem @vcorem name and we can assume that he uses other big names in the crypto industry too. He just scammed one of the community member for 1500$ ! Do not send to anyone money without a proof of call and making sure that he is the right person. Be careful on telegram and save your money from scammers.

Hi @everyone kaspad v0.11.13 is out: https://github.com/kaspanet/kaspad/releases/tag/v0.11.13 This is a major version release with pretty much content as can be seen in the changelog. Most importantly, this version addresses the major underlying issue which troubled the network when side-chains were mined and led to the need for the patch 10 workaround. We changed the IBD negotiation algorithm to a more correct one. This required a new p2p version, v5. This means we cannot fix IBD when interacting with old-version nodes, so when communicating with p2p v4 nodes (nodes running patch 10 or v0.11.11 and below), we still apply the patch logic (aka "Avoiding IBD..."). Some fixes in this version have not only a local effect, but should make the propagation of side-chains throughout the net (if such exist) much smoother. I expect them to be nearly unnoticeable if the entire network upgrades to this version. The more nodes use it, the better. You may have not noticed, but we had a dedicated thread under general for testing release-candidates for this version. Many people participated and spent a lot of time testing and giving feedback. I give them all salute, and call for /ktip to them. The version seems very stable thanks to this effort. This version is mandatory. Please do not keep on running patch10 at all. IBD of a fresh v0.11.13 node will fail when syncing from patch10 nodes. Try making sure you sync from an upgraded node in such cases. If you feel like you upgraded and things are less stable, please report and use --protocol-version=4 in the kaspad cmd line. Do not use patch10.