KasSigner

Broadcast a 2-of-3 multisig on $KAS mainnet tonight using the @KaspaCurrency PSKT/PSKB wire format end-to-end, with no custom intermediate representation. TX 407d948930db9cf5ca77eb0448f0a64182643fcaded423a752a5aebfc86e8c4e Block acceptance in 752 ms. Three Kaspa-specific behaviors that aren't documented anywhere wallet authors can easily find them, surfaced during the debugging: 1. P2SH input sigOpCount must equal N (cosigner count), not M 2. No Bitcoin OP_0 dummy in the CHECKMULTISIG unlock script 3. PartialSig carries the signature variant tag { "schnorr": ... } All three fail-close at broadcast (node rejects before anything touches the chain). No fund-loss path. But any future Kaspa wallet author porting PSBT-multisig logic from Bitcoin tooling will hit them. Drafted a KIP that documents these conventions alongside derivation paths, pubkey sort order, two-layer descriptor, and an optional compact-transport appendix for sub-$20 hardware signers with constrained cameras. Collaborators welcome. KIP draft: github.com/kaspanet/kips/… Explorer: kaspa.stream/tx/407d948930d… #Kaspa #PSKT😎🤟🏼 InKasWeRust

@Max143672 @kaspacurrency Pushed. PR #39 now has the corrected sigOpCount rule plus a source-verified audit pass. github.com/kaspanet/kips/…

Actually It's a little bit more complex. Formally it's fine to use N for sigop count, but it's less efficient than could be. Kaspa has runtime Sig counter. Meaning if the script needs to verify 5 signatures during execution path it's allowed to pass 5 as sigop count. Another thing that should be considered is that order matters and it tries to probe signature for corresponding keys, the correct way to say m <= sigopcount <= n. The algo itself is here #L488" target="_blank" rel="nofollow noopener">github.com/kaspanet/rusty…. In the codebase there's also a way for simulating of tx input validation, that returns what count may be used #L144" target="_blank" rel="nofollow noopener">github.com/kaspanet/rusty…

Broadcast a 2-of-3 multisig on $KAS mainnet tonight using the @KaspaCurrency PSKT/PSKB wire format end-to-end, with no custom intermediate representation. TX 407d948930db9cf5ca77eb0448f0a64182643fcaded423a752a5aebfc86e8c4e Block acceptance in 752 ms. Three Kaspa-specific behaviors that aren't documented anywhere wallet authors can easily find them, surfaced during the debugging: 1. P2SH input sigOpCount must equal N (cosigner count), not M 2. No Bitcoin OP_0 dummy in the CHECKMULTISIG unlock script 3. PartialSig carries the signature variant tag { "schnorr": ... } All three fail-close at broadcast (node rejects before anything touches the chain). No fund-loss path. But any future Kaspa wallet author porting PSBT-multisig logic from Bitcoin tooling will hit them. Drafted a KIP that documents these conventions alongside derivation paths, pubkey sort order, two-layer descriptor, and an optional compact-transport appendix for sub-$20 hardware signers with constrained cameras. Collaborators welcome. KIP draft: github.com/kaspanet/kips/… Explorer: kaspa.stream/tx/407d948930d… #Kaspa #PSKT😎🤟🏼 InKasWeRust

Hey, thanks for your response... you are 100% right, my bad. Read through get_sig_op_count and op_check_multisig_schnorr_or_ecdsa at the links. the rule is M ≤ sig_op_count ≤ N. Since the KIP already requires lex-sorted pubkeys in the redeem script and signatures supplied in that same order, every partial sig matches on its first pubkey try at validation time — consume exactly M sig ops. So it's M, not N. I'll amend the KIP: - sig_op_count = M when cosigners follow the lex-sort + ordered-emission conventions (both already in the KIP) - N as always-safe upper bound Will push a follow-up commit to PR #39 tomorrow. 🙌🏼

@xximpod @KaspaHonest Thanks for the great work… @hus_qy will be great too, but he’s out of the media I suppose.

Thank you everyone for your suggestions! Here is the plan moving forward - Because of ongoing X DM issues (messages simply aren’t reaching people reliably anymore), so have decided to start posting publicly about our guest openings going forward. On Kaspa Core front - where we at currently with some of the brilliant minds: @hashdag – We reached out publical (no response) x.com/xximpod/status… x.com/xximpod/status… @michaelsuttonil – Covenants++ (politely declined earlier due to being very busy) @OriNewman – SilverScript (no response yet) @hus_qy – ZK (no DM’s allowed) would love to discuss and focus on ZK  @coderofstuff_ – (declined earlier) If we missed anyone please let us know. Outside of core, these are other couple of topics we are waiting on- @KaspaKii - on Warpcore  Kaspa L1 & Kaspa L2s together - x.com/xximpod/status… As always, our focus is no hype / no price action just real honest passionate conversation.

@kapsacoin @yenyasuyabaiyo @brt2412 @OrangutanElder Not the same HW… it will be a pain in the ass do that on a raspberry-pi due to crates and libraries… but hey, do it by yourself. I’ll be watching 😎🤟🏼

@yenyasuyabaiyo @brt2412 @OrangutanElder @KasSigner Not yet but I’lll gather the parts soon and build one. I own several seedsigners and thought it was the same hw.

@KasSigner @brt2412 @OrangutanElder 👀👀 oh cooooool

@kapsacoin @brt2412 @OrangutanElder A steganographic way of hiding seeds on images 😎🤟🏼

@KasSigner @brt2412 @OrangutanElder What’s STEGO? :D

@kapsacoin @brt2412 @OrangutanElder That’s it… and try the stego jpeg mode… you will love that 😎🤟🏼

@KasSigner is the option for the most paranoid (my fav). Get your QR code seed phrase engraved or stamped on a metal plate with an offline raspberry pi zero seedstamper, this is your seed. Import seed via camera and sign transaction 100% offline and airgapped. Raspberry pie zero has no Bluetooth, WiFi. The only 100% safe method. Also very safe seed generation via TRNG using a picture of the built in camera as a source of entropy. Seedless is a big no go for me.

@KaspaFuturist Y_outube.com/watch?v=bhsAnXvNAzY

@KasSigner nice video. what is the direct YouTube URL?

KasSigner 2/3 Multisig on Youtube… Your keys, your coins, your miner, your node… InKasWeRist 😎🤟🏼 m.youtube.com/watch?v=bhsAnX…

@brt2412 @KaspaYO @OrangutanElder 😱Great to hear that… So, trust yourself. … do not trust others , don’t let them manage your private keys. Touch some grass .. 🤟🏼

Awesomeness at its finest! $KAS

@KasSigner i'm waiting

Amazing! @KeystoneWallet, please have a look at this. It might help you in your current #Kaspa development.

@KasSigner Wow... #Kaspa always amazes daily.

@KasSigner 🔥🔥🔥

This is amazing fr 👏

Awesome new self sovereign way to sign your own Kaspa transactions! $KAS