Agreed… free the nsec

https://github.com/nostr-protocol/nips/pull/1842

nostr:nevent1qqsfaga4w9nzdfq3pr5ft49608ln2k0mjtnt9guxchjhs52e87j0lfgppamhxue69uhkztnwdaejumr0dsndphet

Better nsec protection / wider interoperability for Nostr as an identity signing system:

https://github.com/nostr-protocol/nips/pull/1842

Yeah yeah yeah

Free the nsec

https://github.com/nostr-protocol/nips/pull/1842

Wait till Cashu.me supports tokens natively locked to npub:

https://primal.net/e/nevent1qvzqqqqqqypzpnkq73xs6exkm8t6rjzvxv84gel82txgkpjlwg8gwjsta5w9g9kjqyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgz72p84u3wytqjex4fl07spmc3m5xm6vwp34kmd47467nr9438kygprqpp7

nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x As you guys are leading the way on supporting Schnorr signing outside of the structure of Nostr events, I’d appreciate your thoughts on a “standard” method signature that is future proof which all signers could adopt… if we can convince fiatjaf to include as optional in NIP07/46… or adopt informally if not. As above, it might be better renamed to avoid issues with your established method.

The current iteration is mostly aligned with Alby existing except expects a raw message string.

https://github.com/nostr-protocol/nips/pull/1842

If I was drafting the method from scratch for NIP07/46, it would return all the data needed to do checks and verification on what was signed and who by eg:

async function signString(message: string) : {hash, sig, pubkey} // sha256 hash of message, Schnorr sig of hash, pubkey of signer

Nostr events are always presented in raw form for signing, and I believe it is probably safer to present the raw string for signing too so user can be sure they are not signing something unintended or malicious that might lose them money (eg a bitcoin transaction)

eg, for a Cashu P2PK token, the raw string would be something like:

[\"P2PK\",{\"nonce\":\"859d4935c4907062a6297cf4e663e2835d90d97ecdd510745d32f6816323a41f\",\"data\":\"0249098aa8b9d2fbec49ff8598feb17b592b986e62319a4fa488a3dc36387157a7\",\"tags\":[[\"sigflag\",\"SIG_INPUTS\"]]}]

Sometimes comedy writes itself

Question nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0s0pfy4z - why does your signer take the sha256 hash as the input (sigHash), rather than the raw string to sign?

It would be better for people to SEE what they are signing for, instead of just a random hash string... the method could then hash for signing.

Nostly Cashu Redeem now supports the nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0s0pfy4z Extension for signing P2PK locked tokens. So you can use it instead of entering your nsec.

https://www.nostrly.com/cashu-redeem/

It's the ONLY Nostr extension I'm aware of that currently supports Schnorr signing.

Hopefully more will in time.... FREE THE SCHNORR!

https://github.com/nostr-protocol/nips/pull/1842

#nostr #cashu #bitcoin #schnorr #p2pk #nut11

Trying my best as a Gen X

Sorry, not sorry 😂󠅓󠅑󠅣󠅘󠅥󠄲󠅟󠄢󠄶󠅤󠅕󠄳󠄺󠅟󠅔󠄸󠅂󠅧󠅓󠅪󠅟󠅦󠄼󠄢󠄡󠅠󠅒󠅞󠅁󠅥󠅒󠅇󠅜󠅥󠅑󠅇󠄺󠅠󠅔󠄸󠄽󠅥󠅉󠄢󠄶󠅪󠅑󠄳󠄩󠄳󠅑󠅈󠅂󠅚󠅒󠄢󠅜󠅥󠅉󠅈󠅆󠅚󠅓󠄢󠄶󠄠󠅉󠅈󠅃󠄲󠅟󠅝󠄶󠅠󠅃󠄱󠄲󠅁󠄲󠅆󠄴󠅧󠅃󠅅󠄶󠄷󠅉󠅈󠄳󠄴󠅠󠄷󠄶󠅘󠄵󠄷󠄶󠅪󠅕󠄵󠄱󠄥󠄿󠅄󠅆󠅜󠄾󠄷󠅆󠅜󠅉󠅄󠅔󠅙󠄽󠅪󠄽󠄥󠄽󠅪󠅉󠅨󠅉󠄢󠅉󠅨󠄿󠅄󠅉󠅨󠅊󠄴󠄹󠅨󠄾󠅪󠅓󠄤󠄾󠄴󠅅󠄤󠄾󠅚󠅛󠅧󠅊󠅄󠄺󠅜󠅊󠅄󠄶󠅝󠄽󠄴󠄱󠄥󠄿󠄴󠅉󠅧󠄿󠅄󠅓󠅩󠅉󠅄󠅔󠅝󠄽󠄴󠅁󠄥󠄾󠄷󠅁󠅨󠄿󠄴󠅜󠅚󠄾󠄴󠄲󠅘󠅉󠅇󠄾󠅉󠄹󠅁󠄺󠄢󠄥󠅡󠄼󠅗󠅉󠅝󠅣󠄢󠄷󠄲󠅛󠅕󠄱󠄣󠅒󠅛󠅠󠅧󠄾󠄶󠅡󠄧󠄡󠄣󠅂󠄝󠄷󠅄󠄵󠄦󠅂󠅝󠅣󠄢󠅇󠄼󠅧󠄧󠅔󠄺󠅞󠅇󠄶󠅛󠅟󠄢󠄶󠅜󠅇󠄳󠄱󠅠󠄽󠅉󠅙󠅠󠅢󠅢󠅝󠄸󠅩󠄩󠄲󠅢󠄨󠅨󠅆󠅂󠄾󠅉󠅉󠅜󠅧󠅚󠅟󠄸󠄩󠄹󠅚󠄺󠅛󠄱󠅗󠅗󠅣󠅞󠅦󠅤󠄡󠄳󠅤󠅩󠅓󠅝󠄶󠅪󠅇󠄳󠄲󠅘󠄨󠄼󠅣󠅠󠅝󠅟󠅩󠅒󠅟󠄧󠅁󠅘󠅕󠅙󠅄󠅇󠄣󠅩󠄦󠅤󠄿󠅈󠅣󠄼󠅚󠅩󠅈󠅟󠄝󠅕󠄢󠅊󠄴󠄽󠅗󠄱󠅩󠅟󠅇󠅃󠄤󠄷󠄶󠅩󠅇󠄳󠄲󠅏󠄺󠄿󠄱󠅕󠅂󠅔󠅑󠄠󠄻󠄨󠄢󠅒󠄺󠄝󠄦󠄻󠄠󠅅󠅘󠅩󠅆󠄻󠅥󠄡󠄶󠅞󠅉󠅦󠅥󠅄󠅘󠅥󠅓󠅆󠅞󠅔󠄢󠄱󠅣󠅄󠅇󠅑󠅂󠅘󠅉󠅁󠅂󠅘󠅓󠄣󠅘󠄱󠅊󠄴󠄲󠅛󠄿󠅇󠅊󠅜󠄾󠄢󠅆󠅝󠅉󠅝󠄺󠅝󠄾󠅪󠅘󠅚󠄽󠅪󠅓󠄡󠅊󠅄󠄽󠄥󠄽󠄢󠄶󠅛󠅊󠄷󠅊󠅝󠄾󠅇󠅂󠅛󠄽󠅇󠄺󠅛󠄾󠅪󠅅󠅪󠄾󠅚󠅂󠅛󠄽󠄴󠅅󠅨󠄽󠄴󠄵󠅧󠅉󠅪󠄹󠄤󠄾󠅇󠅅󠄤󠄾󠅪󠄾󠅘󠄿󠅄󠄾󠅝󠄾󠅪󠄵󠄤󠄽󠅄󠅗󠄢󠅊󠅝󠄶󠅚󠅇󠄳󠄵󠄳󠅑󠅤󠄥󠄲󠄝󠄾󠅤󠄠󠅡󠄷󠄝󠄻󠅒󠄣󠄵󠅗󠅂󠅝󠅣󠅃󠄿󠅏󠄻󠄹󠅟󠅆󠄲󠄴󠄼󠅝󠄠󠅚󠄧󠄺󠅝󠄩󠅠󠅢󠅖󠅘󠅠󠄱󠅘󠅘󠅊󠄻󠄾󠅘󠅊󠅆󠅗󠅗󠄣󠅀󠅔󠅏󠅡󠅀󠅖󠄝󠄝󠅇󠅇󠄸󠄽󠅏󠄥󠅑󠅇󠄼󠅒󠅕󠄶󠅖󠄤󠅓󠄽󠄱󠄶󠅓󠅜󠄨󠅤󠅛󠅢󠄲󠄝󠄾󠅤󠅠󠅟󠅚󠄦󠅃󠅨󠅘󠅓󠄡󠅗󠅗󠅣󠄺󠅣󠄧󠅘󠄷󠄻󠄻󠅚󠄶󠅇󠅑󠅓󠅇󠄧󠅤󠅆󠅅󠄝󠅙󠄺󠅩󠄿󠄿󠅢󠅜󠅆󠅤󠅖󠅑󠅊󠅥󠅦󠄻󠅔󠅧󠅑󠄿󠅡󠅗󠄸󠄥󠄥󠅘󠅓󠅜󠅗󠅗󠅈󠄤󠅕󠄾󠄨󠅟󠅧󠄨󠄹󠅏󠄢󠄳󠄹󠅝󠄥󠄢󠅩󠅅󠅗󠅩󠄳󠅙󠅦󠅜󠅛󠅀󠄥󠄻󠄤󠅞󠅨󠅚󠅩󠅦󠄾󠄷󠅣󠅘󠄳󠅅󠅗󠅅󠄷󠅛󠅉󠅇󠄵󠄲󠅉󠅈󠄾󠄤󠅁󠄴󠅉󠅩󠄽󠅄󠅓󠅧󠄾󠄷󠅉󠄠󠅉󠅇󠅅󠅪󠄾󠅝󠅆󠅜󠄾󠅄󠄱󠄥󠄾󠄢󠄵󠄤󠅊󠅚󠅜󠅛󠅉󠅪󠅆󠅘󠄾󠅄󠅛󠄥󠄾󠅪󠅅󠅩󠄽󠅚󠄵󠄣󠄾󠅪󠅁󠄣󠅊󠄷󠄹󠄠󠅊󠅄󠄵󠅪󠅊󠅇󠅅󠅩󠅉󠅄󠄲󠅙󠅊󠄴󠅂󠅜󠄾󠅄󠅓󠄢󠄾󠄷󠅅󠄤󠄽󠄴󠅗󠄥󠅉󠅪󠄲󠅘󠅉󠄡󠅗󠅘󠄱󠅝󠅒󠅄󠄺󠅞󠄧󠅨󠅓󠄨󠄶󠅉󠄸󠄾󠅚󠅥󠄴󠅔󠅥󠅢󠄹󠅅󠅡󠄢󠅠󠅀󠅊󠅪󠄻󠄵󠄳󠅥󠄠󠄣󠅇󠅗󠅈󠄺󠅣󠄡󠄥󠅧󠅕󠅗󠅉󠅇󠅃󠅚󠅉󠅇󠅆󠅉󠄹󠄽󠅖󠄳󠅃󠄣󠄼󠄾󠄵󠅥󠅠󠄩󠅔󠄺󠄼󠅊󠄣󠅤󠅢󠅣󠄻󠄤󠅖󠅤󠅥󠄤󠅂󠅉󠅂󠄼󠅀󠄱󠅢󠅂󠅤󠅒󠄩󠄸󠄼󠅁󠅗󠅔󠅁󠅙󠅉󠅈󠄾󠅉󠄹󠄵󠅤󠅛󠄱󠅀󠅘󠅅󠅟󠅀󠄼󠅊󠅂󠄠󠅜󠄿󠄼󠅩󠅪󠄻󠄱󠅢󠅛󠅣󠅃󠅄󠅒󠄶󠄵󠄸󠄴󠅢󠅥󠅊󠄤󠅓󠄡󠄳󠅇󠅃󠅖󠅡󠄳󠅑󠅉󠅈󠄺󠅉󠄹󠄾󠄸󠅕󠅩󠅞󠄽󠄳󠄧󠅦󠅄󠄷󠄱󠄵󠅗󠄨󠅡󠅣󠄽󠄿󠅕󠅓󠅖󠄴󠅡󠅂󠄽󠅕󠅡󠅡󠅠󠅜󠄢󠅇󠄶󠅖󠅀󠅒󠄹󠄦󠄲󠄼󠅉󠄹 !!!

https://primal.net/e/nevent1qqs8f636fl20ejmcnrdswe8wtjur48qru0kawfsrswfd3hmx63g55cswnt5rz

Yes, cashu mints want a Schnorr signature on a structured string… signers create signatures on a event, changing the structure that gets signed.

Need to convince fiatjaf to add signSchnorr() to Nostr NIPS-07/46:

https://github.com/nostr-protocol/nips/pull/1842

Understandable. There is a standalone opensource version you can download, inspect and run from your computer.

https://github.com/robwoodgate/cashu-redeem

It's a bit bleeding edge... and you need to use your nsec to decode them as Nostr doesn't specify signers can create schnorr signatures outside of events.

Paste into Nostrly Cashu Redeem (either online or the standalone version) to check you copied emoji out ok - sometimes Primal can break them at the see more... so generally best to copy the entire note.

If the token reads ok, you can enter your nsec and a lightning address to redeem it to.

Cashu.me wallet will shortly allow redemption straight to Cashu wallet.

You have to login to 0x using your nsec.

You'll need to use:

https://github.com/robwoodgate/cashu-redeem

or

https://www.nostrly.com/cashu-redeem/

or

0xchat.com

or wait a few more days for Cashu.me to support redemption:

https://primal.net/e/nevent1qvzqqqqqqypzpnkq73xs6exkm8t6rjzvxv84gel82txgkpjlwg8gwjsta5w9g9kjqyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgz72p84u3wytqjex4fl07spmc3m5xm6vwp34kmd47467nr9438kygprqpp7