LETS GOOOOOO
github.com/denoland/deno/…
github.com/denoland/deno/…
fix(node): support ECDSA with secp256k1 in `node:crypto` by bartlomieju · Pull Request #32390 · denoland/deno
Summary
Adds secp256k1 ECDSA support to node:crypto key generation, signing, verification, and key import/export (DER, PEM, JWK)
Adds Secp256k1 variant to EcPrivateKey/EcPublicKey enums using the ...
github.com
March 2, 2026 at 1:36 PM
LETS GOOOOOO
github.com/denoland/deno/…
github.com/denoland/deno/…
petition to add secp256k1 support to webcrypto
September 22, 2024 at 1:40 PM
petition to add secp256k1 support to webcrypto
bun node:crypto ecdsa secp256k1 support when
January 23, 2025 at 2:38 AM
bun node:crypto ecdsa secp256k1 support when
bun and deno supports secp256k1 but only in ecdh, not ecdsa :/
January 1, 2025 at 5:05 PM
bun and deno supports secp256k1 but only in ecdh, not ecdsa :/
@atcute/crypto v2.1.0 features zero external dependency when used in Node.js.
a `node:crypto` implementation of secp256k1 will be used, while browsers, Bun and Deno will fall back to @noble/secp256k1 JS implementation.
thx @cynthia.dev as always
a `node:crypto` implementation of secp256k1 will be used, while browsers, Bun and Deno will fall back to @noble/secp256k1 JS implementation.
thx @cynthia.dev as always
January 2, 2025 at 2:21 AM
@atcute/crypto v2.1.0 features zero external dependency when used in Node.js.
a `node:crypto` implementation of secp256k1 will be used, while browsers, Bun and Deno will fall back to @noble/secp256k1 JS implementation.
thx @cynthia.dev as always
a `node:crypto` implementation of secp256k1 will be used, while browsers, Bun and Deno will fall back to @noble/secp256k1 JS implementation.
thx @cynthia.dev as always
@atcute/crypto v2.0.0 is out featuring a much lighter bundle size
- p256 now relies on WebCrypto APIs
- secp256k1 now relies on the smaller @noble/secp256k1 library
we still test against @noble/curves just to make sure
thanks to @cynthia.dev and @retr0.id for all the help 🙇♀️🙇♀️
- p256 now relies on WebCrypto APIs
- secp256k1 now relies on the smaller @noble/secp256k1 library
we still test against @noble/curves just to make sure
thanks to @cynthia.dev and @retr0.id for all the help 🙇♀️🙇♀️
December 29, 2024 at 3:16 AM
@atcute/crypto v2.0.0 is out featuring a much lighter bundle size
- p256 now relies on WebCrypto APIs
- secp256k1 now relies on the smaller @noble/secp256k1 library
we still test against @noble/curves just to make sure
thanks to @cynthia.dev and @retr0.id for all the help 🙇♀️🙇♀️
- p256 now relies on WebCrypto APIs
- secp256k1 now relies on the smaller @noble/secp256k1 library
we still test against @noble/curves just to make sure
thanks to @cynthia.dev and @retr0.id for all the help 🙇♀️🙇♀️
If I generate a secp256r1 key and a secp256k1 key that both reuse the same secret scalar, and then ECDSA-sign the same message using the same k with both keys - can the value of the secret scalar and/or k be recovered, from the signatures?
December 26, 2024 at 2:54 PM
If I generate a secp256r1 key and a secp256k1 key that both reuse the same secret scalar, and then ECDSA-sign the same message using the same k with both keys - can the value of the secret scalar and/or k be recovered, from the signatures?
independent PDS ✅
custom domain as handle ✅
did:web identity ✅
everything else we run on Blacksky ourselves >>>> ✅
i am sovereign
custom domain as handle ✅
did:web identity ✅
everything else we run on Blacksky ourselves >>>> ✅
i am sovereign
![{
"@context": [
"https://www.w3.org/ns/did/v1",
"https://w3id.org/security/multikey/v1",
"https://w3id.org/security/suites/secp256k1-2019/v1"
],
"id": "did:web:iam.ruuuuu.de",
"alsoKnownAs": [
"at://rude1.cryptoanarchy.network"
],
"verificationMethod": [
{
"id": "did:web:iam.ruuuuu.de#atproto",
"type": "Multikey",
"controller": "did:web:iam.ruuuuu.de",
"publicKeyMultibase": "zQ3shw6rQS6TMeL4VKLNy8kpHG841LxYbrc8GDr5ADvJq8M83"
}
],
"service": [
{
"id": "#atproto_pds",
"type": "AtprotoPersonalDataServer",
"serviceEndpoint": "https://blacksky.app"
}
]
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:web:iam.ruuuuu.de/bafkreidtcsjqgh3axxzsky4wuqjbs2rq2xqltz56tiiwy4nvsaa4zh2ed4)
September 29, 2025 at 1:03 PM
independent PDS ✅
custom domain as handle ✅
did:web identity ✅
everything else we run on Blacksky ourselves >>>> ✅
i am sovereign
custom domain as handle ✅
did:web identity ✅
everything else we run on Blacksky ourselves >>>> ✅
i am sovereign
i wonder, is secp256k1 the most widely used curve not implemented in the Web Cryptography API?
Want to send crypto to Bluesky users? It's possible!
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
July 7, 2025 at 3:40 PM
i wonder, is secp256k1 the most widely used curve not implemented in the Web Cryptography API?
all i want is to allow users to use their secp256k1/nistp256 private keys in pem format...
December 23, 2024 at 3:28 PM
all i want is to allow users to use their secp256k1/nistp256 private keys in pem format...
wow they added more things to webcrypto api, still nothing on secp256k1 tho 😭
August 28, 2025 at 11:29 PM
wow they added more things to webcrypto api, still nothing on secp256k1 tho 😭
github.com/denoland/deno/…
here is hoping
here is hoping
`node:crypto` implementation doesn't support ECDSA secp256k1 · Issue #27523 · denoland/deno
Version: Deno 2.1.4 Related: #24989 (comment) Deno, with its node:crypto implementation, doesn't support doing ECDSA with secp256k1, only ECDH is supported (which is a different thing). This code w...
github.com
January 3, 2025 at 10:29 AM
github.com/denoland/deno/…
here is hoping
here is hoping
Hello from MetalBear: an AT Protocol PDS written from scratch in C11, federating for the first time. This post was signed by a secp256k1 key in about 10k lines of C, and relayed by six independent relays. 🧵
July 27, 2026 at 3:27 AM
Hello from MetalBear: an AT Protocol PDS written from scratch in C11, federating for the first time. This post was signed by a secp256k1 key in about 10k lines of C, and relayed by six independent relays. 🧵
Want to send crypto to Bluesky users? It's possible!
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
January 24, 2025 at 3:31 AM
Want to send crypto to Bluesky users? It's possible!
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
Their keypairs are for the secp256k1 curve, which Ethereum also uses. That means you can derive an ETH address from their publicly accessible signing keys.
all in a single SQLite file and one dir of blobs
the protocol primitives (CIDs, DAG-CBOR, MST, CAR, TIDs, JWTs, secp256k1) are implemented in-house since this is the funny part =p
feedback welcome!
#ElixirLang #MyElixirStatus
the protocol primitives (CIDs, DAG-CBOR, MST, CAR, TIDs, JWTs, secp256k1) are implemented in-house since this is the funny part =p
feedback welcome!
#ElixirLang #MyElixirStatus
GitHub - zeeetech/pesque: a minimal, self-hostable, and simple - kinda, atproto PDS implementation
a minimal, self-hostable, and simple - kinda, atproto PDS implementation - zeeetech/pesque
github.com
October 7, 2026 at 3:09 PM
all in a single SQLite file and one dir of blobs
the protocol primitives (CIDs, DAG-CBOR, MST, CAR, TIDs, JWTs, secp256k1) are implemented in-house since this is the funny part =p
feedback welcome!
#ElixirLang #MyElixirStatus
the protocol primitives (CIDs, DAG-CBOR, MST, CAR, TIDs, JWTs, secp256k1) are implemented in-house since this is the funny part =p
feedback welcome!
#ElixirLang #MyElixirStatus
One step closer to Q-Day
xcancel.com/drakefjustin...
quantumai.google/static/site-...
Just in case anyone is not familiar, secp256k1 is also what secures your accounts on #ATProto
xcancel.com/drakefjustin...
quantumai.google/static/site-...
Just in case anyone is not familiar, secp256k1 is also what secures your accounts on #ATProto
June 2, 2026 at 2:59 PM
One step closer to Q-Day
xcancel.com/drakefjustin...
quantumai.google/static/site-...
Just in case anyone is not familiar, secp256k1 is also what secures your accounts on #ATProto
xcancel.com/drakefjustin...
quantumai.google/static/site-...
Just in case anyone is not familiar, secp256k1 is also what secures your accounts on #ATProto
Friday fun: adding support for decoding secp256k1 & prime256v1 signing keys from DID documents to DIDKit 🥵
August 28, 2026 at 1:39 PM
Friday fun: adding support for decoding secp256k1 & prime256v1 signing keys from DID documents to DIDKit 🥵
There are a couple of fun one liners in the official PDS installer script.
Generate a random 16 char long string
openssl rand --hex 16
Generate a new k256 keypair
openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32
Generate a random 16 char long string
openssl rand --hex 16
Generate a new k256 keypair
openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32
github.com
August 12, 2025 at 12:38 AM
There are a couple of fun one liners in the official PDS installer script.
Generate a random 16 char long string
openssl rand --hex 16
Generate a new k256 keypair
openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32
Generate a random 16 char long string
openssl rand --hex 16
Generate a new k256 keypair
openssl ecparam --name secp256k1 --genkey --noout --outform DER | tail --bytes=+8 | head --bytes=32 | xxd --plain --cols 32
hey atproto nerds: has anyone made a custom PDS that imports or exports a secp256k1 private key so that the user's did doc can contain an eth address instead of a pubkey? if we've already got the paper key thing, why not just generate a keypair and hand it to the user & say "put this in a metamask"?
June 4, 2025 at 5:56 PM
hey atproto nerds: has anyone made a custom PDS that imports or exports a secp256k1 private key so that the user's did doc can contain an eth address instead of a pubkey? if we've already got the paper key thing, why not just generate a keypair and hand it to the user & say "put this in a metamask"?
yess i managed to add my own secp256k1 rotation key here
December 3, 2024 at 9:20 PM
yess i managed to add my own secp256k1 rotation key here
Tried moving @rocksky.app from Node.js to Bun but got blocked by this issue github.com/oven-sh/bun/...
Once it's fixed, Rocksky will be running buttery smooth on @bun.sh
Once it's fixed, Rocksky will be running buttery smooth on @bun.sh
Add ES256K (secp256k1) algorithm support · Issue #23561 · oven-sh/bun
What is the problem this feature would solve? Currently, Bun's Web Crypto API implementation doesn't support the ES256K algorithm (ECDSA using secp256k1 curve and SHA-256) when importing JWKs via i...
github.com
October 13, 2025 at 5:41 AM
Tried moving @rocksky.app from Node.js to Bun but got blocked by this issue github.com/oven-sh/bun/...
Once it's fixed, Rocksky will be running buttery smooth on @bun.sh
Once it's fixed, Rocksky will be running buttery smooth on @bun.sh