"Mom! Mom! Moooom! Mom!!!"
"I'm here darlin, what?"
"Come here, look what I made."
"What is it?"
"Look! Ecosystems, real local ecosystems. They even think they have free will!"
"Where did you lau...
Just curious, what's the next step in your repo extraction quest after extracting the huge scary `site.txt`? It appears to be a frontend js without some ready way to load it.
Verification script fails with `Error: "publicKey" expected Uint8Array of length 32, got type=string` for me. What's the pubkey format expected? Tried hex as txt and as binary. I wouldn't load the pubkey from file at all if possible.
It also fails with `ERR_PACKAGE_PATH_NOT_EXPORTED` to me unless the following changes are made:
```patch
-import { sha256 } from "@noble/hashes/sha2";
-import { schnorr } from "@noble/curves/secp256k1";
+import { sha256 } from "@noble/hashes/sha2.js";
+import { schnorr } from "@noble/curves/secp256k1.js";
```
Thanks for building the weird thing anyway, it's interesting.
Verification script fails with `Error: "publicKey" expected Uint8Array of length 32, got type=string` for me. What's the pubkey format expected? Tried hex as txt and as binary. I wouldn't load the pubkey from file at all if possible.
It also fails with `ERR_PACKAGE_PATH_NOT_EXPORTED` to me unless the following changes are made:
```patch
-import { sha256 } from "@noble/hashes/sha2";
-import { schnorr } from "@noble/curves/secp256k1";
+import { sha256 } from "@noble/hashes/sha2.js";
+import { schnorr } from "@noble/curves/secp256k1.js";
```
Thanks for building the weird thing anyway, it's interesting.
1