I don't think proof of work on pubkeys is the best way to implement a cost on new accounts - mostly because it's not compatible with existing accounts.
Adding a new action kind that applies proof of work to existing pubkeys might be a better way to go.
maybe ProofOfWork(existingpubkey + nonce)
Also SHA256 is not a great choice for the proof of work - it will require purchasing the pow from an ASIC hashpower supplier.
Better to have something that can be run more efficiently on desktop or mobile - maybe RandomX. That way people can create their own pow to apply to their keys.
#nostr
FreeTrade /
npub166…ne05s
2022-12-30 09:27:55
Author Public Key
npub166t8ztecr47xy99pft39wty0z7p2nrtq03pxz5ek3dvylwcwpajs3ne05sPublished at
2022-12-30 09:27:55Event JSON
{
"id": "1a4ae881424ea9f49e95588fa260096380f15a295a3d4549069b86994ba4e37b",
"pubkey": "d696712f381d7c6214a14ae2572c8f1782a98d607c426153368b584fbb0e0f65",
"created_at": 1672392475,
"kind": 1,
"tags": [],
"content": "I don't think proof of work on pubkeys is the best way to implement a cost on new accounts - mostly because it's not compatible with existing accounts.\n\nAdding a new action kind that applies proof of work to existing pubkeys might be a better way to go.\n\nmaybe ProofOfWork(existingpubkey + nonce)\n\nAlso SHA256 is not a great choice for the proof of work - it will require purchasing the pow from an ASIC hashpower supplier.\nBetter to have something that can be run more efficiently on desktop or mobile - maybe RandomX. That way people can create their own pow to apply to their keys.\n\n#nostr\n",
"sig": "335462cac9523bf435900c1ec2a359a14c31ed4cb85f9b81b2b9103abac5bd0ed283f8c149d5f0c93fc9f0fbd539638e774f1ae240ee60dd58c1d79eb01aa521"
}