We are so proud to sponsor @ExTriage on his awesome push to get the Kaspa Rally Car to the start line!
If you want to support this valiant effort then you can sponsor him at staghunt.app
$KAS
KommsApp retweeted
Thursday is nearly here! Time for X's best #Bittensor and #Kaspa space! Join @HeavyHashMedia @Tao_mans_son and myself as we go over all things $TAO & $KAS on our @BlockchainBants show.
What's your favourite saying to tao or kas pill someone?
Every Thursday at a new start time of 8pm UK time
Set a reminder for the Space! xitter.cf/i/spaces/1MJgNbLVqlbGL
Komms can help the Construction industry?!
But how?
On a big site, the dispute is rarely about the work. It's about which drawing revision the electrician, plumber, bricklayer etc had and when.
Komms could give every main contractor one workspace: encrypted drawings of any size, tamper-proof timestamped records, and no per-seat fees for extra trades.
kaspa:native bittensor:native
Komms solves this persistent pain point.
We don’t data harvest so we don’t even need your email.
You can create a Komms account with just a Passkey.
$KAS $TAO
A new data breach involving Double Counter has exposed information connected to Discord users affecting around 275,000 unique email addresses.
According to Have I Been Pwned, the exposed data includes:
-Email addresses
-Discord usernames
-Names
-Geographic information
-Country and postcode for some paying subscribers
The breach was linked to a vulnerability in Metabase, the analytics platform used by Double Counter.
If you’ve used Double Counter on Discord, check whether your email was affected and stay alert for phishing attempts or suspicious Discord messages.
Readers added context they thought people might want to know
Important clarification as the majority of people are misunderstanding this post.
Double Counter is a third party application used to detect alternative discord accounts. Discord themselves have nothing to do with this, Double Counter was breached, not Discord.
doublecounter.gg/blog/security-…
haveibeenpwned.com/Breach/DoubleC…
x.com/discord_suppor…
the former category of kaspa protecting covenants feel conceptually much more approachable because numerous analogs elsewhere exist (other chains, tradfi and IRL). It is not difficult to understand spending rules like a timelock or multi-sig or escrow or inheritance etc
As I understand 'stateful covenants' enforce the state of the output child (next generation?) as well as the spending params already explained by the kaspa protecting category of covenants. One simple example we explored for @KommsApp was rate limiting and onchain feature flagging.
So not two distinct categories but rather different levels of complexity i.e. building blocks, features?
And can't we continue this leveling of complexity into multi-covenant products/programs likely having varying interdependences between them?
If your ideas are good they should stand up to scrutiny.
This was a fantastic space. Thanks once again for the great opportunity.
$KAS $TAO
A discussion on the new potential subnet on bittensor:native - @KommsApp , currently in testnet.
With 2 hours of interrogation, the conclusion I came to is that the tech and the product seems utterly refined.
Have a listen to us question @TomHutchinson27 @Chris_Hutch7 and @argonmining to determine how well thought out this subnet is and whether you have any questions me and @HeavyHashMedia have missed!
#bittensor kaspa:native
Who's been waiting for a marriage between #Kaspa and #Bittensor? Well here it is! @KommsApp
Blockchain Banter - Beyond The Block Ep.8 - Komms, A Decentralized Communication and Coordination Protocol built on Bittensor and Kaspa
Join @HeavyHashMedia
@Tao_mans_son and myself as we take a deep dive, and interview the team behind @KommsApp
This thursday at 9pm UK time
Set a reminder, you don't wanna miss this one! xitter.cf/i/spaces/1dGYlaOEWBNKX
$TAO $KAS @BlockchainBants