You know what day it is.
Blockchain Banter coming to the rescue to make Mondays bearable!
On todays show we’ve got:
@Igra_Labs to walk us through their updated roadmap 👀
@Seb28_7 giving us some more awesome insights into KasMaps 🔥
And the man who is going to one day change the Oracle game Mr @eliottmea 🍻
If you can’t listen live, listen later.
See you there folks
$KAS #Kaspa
@eliottmea@Kaspa_Commons In its current form, as long as the merchant accepts L1 Kaspa assets, we are not limited to KAS.
If @kasplex with KEF integrates USDC on L1 (KRC20), then USDC can be used for payments.
Once @AppKaskad and @kyocard are ready, we’ll also offre other options.
I'm really glad to announce now officially, that the #Ledger Live integration for #Kaspa is released. You can now send & receive $KAS with Ledger Live!
In future there will be a swap possibility in Ledger Live as well, we're working on it actively!
Now let's get this new nice explorer ready...
And then? Next $KAS project? Where do we need #Kaspa to be integrated?
Do we have a good point-of-sale actually?
while butting heads with @CryptoAspect on panic failures in zkVMs I received this <from panic attacks to full night's sleep> newsletter from @chargrysolle.
i saw this as a divine calling to braindump my pov before implementing full night sleep.
for any VM system that implements metering - and for any zkVM system that implements provable metering - panic is a (non) special case requiring no special treatment. sure, one can architect a system which safely handles panic w/o metering, but not the reverse - and since based (rollups or the superior) programs / vprogs necessitate provable metering, panic/abort is "solved" or correctly wrapped for free.
as @Max143672@CryptoAspect point out, SP1 as a single layer zkVM doesn't support (provable metering and doesn't support) panic handling - while this can be patched at the compiler level, this would guarantee safe abort of programs compiled using their toolchain only, whereas permissionless onchain registration of programs requires a more robust guarantee.
the implied conclusion is that based (rollup or the superior) program systems can either use bespoke VMs such as Polygon's and Scroll's zkEVMs, or the slower and less performant nesting of general purpose VMs, which would enable runtime analysis of the guest program.
but researching this I discovered a much neater alternative by @StarkWareLtd - the Sierra raw byte format, which iiuc achieves provable safety (and metering) via compile time static analysis. if true this is very very cool! cc @VolokhIlia
tldr CairoVM>>SP1
--
this discussion is orthogonal or at least complementary to the based vprogs design, a zk variant of Solana's design - the link is somewhere on kaspanet's github - which insists on sync composability on the program layer while allowing programs to live and maintain their own state - their own mini zkVMs.
vprogs optimize for dapp sovereignty, and will obviate the inherently parasitic L2 network/rollup entities which seek to lock and suck all dapp activity under their umbrella.
hopefully kas builders will optimize for sovereignty too.
cc @michaelsuttonil
This is gonna be a huge one!!
Seriously, make sure you are there!
Massive thanks to @Kaspa_KEF once again for helping to organise such an awesome event
$KAS #Kaspa
KasMap is now live! Not only can you add IRL businesses to the map you can also add yourself as a Kaspian and set meet ups for other Kaspians in your area to see!
A massive thanks to @TheLoadedLounge for all the work that has gone into this.
Go to https://t.co/DkRjEqdvv9 and add yourself to the map to show the world how many Kaspians there really are.
Use referral code: KASPACHRIS
To earn 20 points and to get 10% discount on verification ����
$KAS #Kaspa
IGRA makes decentralized Kaspa Layer 2 possible. We built open-source tools to make running nodes accessible to everyone.
IGRA CLI: Terminal dashboard for node operators. Simple, powerful, free.
https://t.co/E01C079zeY
#Kaspa#Decentralization