Signed Work is a place for creators to issue digitally signed work (sometimes called NFTs) to people, in a safe and secure way.
The system is based on cryptography but doesn't involve blockchains, which means:
- Your signed NFT has the content embedded in it.
- No wasteful use of energy.
- Fraudsters selling counterfeits of other people's work aren't welcome and can be easily banned.
- It's free and easy to use.
Nobody can forge your signature. Not even us. Your secret signing keys are generated in your browser for you to keep privately. Your unique signatures can be verified by others using your certificate.
Our system is open, which means everyone is free (and encouraged) to keep their own copies of all the NFTs, certificates, original work, etc.
We are planning some new features to support creators.
- Payment acceptance for creators.
- Limited edition pieces: a way for creators to offer a limited edition NFT.
- Verified work: we will work with creators on ways to verify that they own the work.
- Counterfeit detection: we will develop ways to quickly detect counterfeit content.
- API documentation to allow the community to develop creator tools, native apps, etc.
- Registration by methods other than twitter.
Join us on Discord
79d246 by @SignedWork issued to @mikekelly85
378db1 by @bitmarx issued to @mikekelly85
39238e by @oknoorap issued to @SignedWork
7c9234 by @0xjim issued to @0xjim
bb1126 by @mm_mm issued to @SignedWork
2e0f51 by @srinusirigina issued to @srinusirigina
c9ccd9 by @srinusirigina issued to @srinusirigina
f109ea by @kidehen issued to @kidehen
- What is your policy on fraud and counterfeits? We will remove content and users that we know are attempting to claim other people's work without their permission. We're working on ways to detect this faster.
- Someone is claiming my work is theirs. What do I do? Email firstname.lastname@example.org with as much detail as possible.
- What payment methods will you support? We will help creators take payment by card and major cryptocurrencies.
- Why do you only support registering with a twitter account? It's just the first option we implemented. More will be added soon!
- Do you have an API? Not yet. It is high up on the roadmap.
How does the tech actually work under the hood? In short:
- A keypair is generated in your browser.
- The keypair is used to issue a Certificate Signing Request (PKCS10) to the network.
- When verification is completed, the network issues an X509 certificate.
- The certificate, the key material, (and the cert chain), is then packaged up into key file the user stores (PKCS12).
- When signing work, the private key is handled locally in browser memory. Signed messages are packaged up with the Cryptographic Message Syntax (PKCS7) and sent to the network.
- All the signed work is standard PKCS7 messages that can be verified using tools like openssl.