SIGit

Secure & Private Agreements

An open-source, self-hostable solution for secure document signing and verification.

Public Key

npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq

NIP-05 Address

Profile Code

nprofile1qqsxhugzf33nvzfmvvkm9k3pkedyf37c9qcy2na56atrfw3grctpeyqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3gamnwvaz7tmjv4kxz7fwwd5kw6t59e5k7qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqzrmhwden5te0dehhxarj9ekk7mg8kq5ta

Publishing to

Author Public Key

npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq

Show more details

Last Notes

2026-04-19 09:27:33 UTC

- reply

Not ours

2026-01-25 21:21:28 UTC

- reply

The challenge is to build a flow that protects both content and metadata, works both online and offline, and is redundant across multiple relays / blossom servers
We have released an MVP but the logic is tied to sigit.io
We are close to the next release in which the logic is encapsulated in state machines and will work seamlessly across clients (encryption, OTS, retries, support for various mark types in pdfs, template agreements, etc)

2026-01-25 21:15:57 UTC

We're making this flow easier to build into other nostr clients through the sigit/core library and the sigit CLI
#nevent1q…fz9h

2026-01-16 21:08:45 UTC

- reply

This works today on sigit.io however in a few weeks we will launch sigit/core - a standalone library that will allow any app to create, sign, or verify a sigit in a completely interoperable fashion (including OTS timestamps and offline flow)

2026-01-15 10:50:45 UTC

## BudaBit Demo Day application
### Title: SIGit CLI
Pitch:
We are rebuilding SIGit to use state machines, bringing the core logic into a standalone library, such that it can easily be used by other projects and clients.
The first client to be released with the new library will be the SIGit CLI, and will be debuted at the Budabit Club event.

2025-10-21 15:27:50 UTC

The next development chapter for SIGit will be the creation of an NPM module to allow others to build SIGits into their tools and applications
As part of this we will be ripping out NDK and replacing with AppleSauce
We are also planning to encapsulate all the logic into State Machines - this will significantly improve stability, usability, and maintainability.
We'd like to thank all of the donors who have supported us so far!

2025-09-09 11:43:46 UTC

Last month we scored a podium finish at the Baltic Honeybadger 2025 Hackathon for @nprofile…24cn, sponsored by @nprofile…jxlh and with funds distributed through @nprofile…j908
Why do you need SIGit? It's simple... legacy providers like docusign store all your files centrally, unencrypted and at risk of being hacked. And to top it off they are advertising the use of AI to scan documents. All this leaves users of centralised contract signing platforms at risk of nefarious actions, of privacy being eroded and of a hostile change in regulatory or government policy leaving you unable to protect your business relationships.
Try us out today at sigit.io
And a huge congrats to the other winners! BlindBit Suite, Receipt Cash and Git Futz
@nprofile…xmsq
@nprofile…5shn
@nprofile…4yr3

2025-09-04 14:48:39 UTC

- reply

Wrong. If you read the legislation on digital signatures, the key must be something the "user can control"
Most solutions use SMS and email, neither of which produces a a signature, and neither of which are under the control of the user
We believe 99% of digital signing solutions are not compliant
We understand your point though, that corporates have more trust in the perceived "legal value" of the cert authorities
We plan to address this point more eloquently as we build out

2025-09-04 08:18:41 UTC

- reply

Indeed, they already do
They don't hide it, they sell it!!
https://www.docusign.com/products/platform/ai
This is impossible in SIGit. A named counterparty has to export an unencrypted version, for it to be used in other tools.

2025-09-04 07:02:20 UTC

Did you know that almost every commercial document signing solution makes your agreement available to third parties?
With records in a database that can be easily modified?
With SIGit, your documents are encrypted in the browser, and are only accessible to named counterparties.
We use Blossom for data storage, Nostr for secure identity and metadata signing, and OTS for timestamping on Bitcoin.
SIGit is available now, and we'd love your feedback!
https://sigit.io

2025-08-18 12:14:30 UTC

- reply

https://archive.ph/kHdIm

2025-08-12 15:34:40 UTC

On-boarding to @nprofile…eyhh today, to which we will receive our prize from a podium hackathon finish at #BH2025
Love the fact that a project is created as part of an OP_RETURN code in an actual bitcoin UTXO
The prize wil be released to us in tranches, if we don't claim, it's time locked and returnable to the investor
Our access key is literally our 12 words
Smooth!!!
https://hub.angor.io/project/angor1q4heck5tf6svq7x8jp5twak329xtv9805xppvq5

2025-08-10 09:30:47 UTC

- reply

Our fundraiser is here: https://geyser.fund/project/sigit

2025-08-10 09:24:43 UTC

We are participating in the HoneyBadger Hackathon, sponsored by Angor!
Below is our first ever demo video
#BH2025
https://vid.ft.hn/w/oWTfZdMapZdxwdwJQTspdk

2025-08-05 11:41:31 UTC

- reply

@nprofile…4qa2, fyi

2025-08-05 11:41:02 UTC

v2.0.7 is now available - this fixes some issues using the offline flow, and makes it possible to verify an unencrypted SIGit from the homepage, without signing in
Nostr works great without internet, or relays 😎
https://git.nostrdev.com/sigit/sigit.io/releases/tag/v2.0.7

2025-08-03 12:54:34 UTC

All counterparty signatures, plus the creation of the SIGit itself, are timestamped (OTS) on the Bitcoin blockchain
Irrefutable proof that an agreement was signed on a particular date
https://sigit.io

2025-07-31 11:45:17 UTC

SIGit v2.0.6 is now released!
A SIGit is composed of multiple regular files (e.g. original files, template.json), unpublished nostr events (e.g. signed create and sign events) and published nostr events (e.g. notification gift wraps, app data).
For performance and reliability, all these files are zipped, encrypted, and loaded to blossom.
For even better performance, to avoid downloading the zip and fetching / processing nostr events each time - the underlying files are also cached in the local browser file cache, the IndexedDB - files repository.
Each time SIGit needs one of these building blocks it first checks the local cache. On cache miss, we check the original decrypted source in cache. If we can't find that, then we download the zip from blossom and decrypt the contents.
Finally, if the blossom zip is missing on the blossom server(s), we fetch the original app data (30078) event and re-process (and publish) all the source events again.
In this release, we improved the stability of the above process.
https://git.nostrdev.com/sigit/sigit.io/releases/tag/v2.0.6

2025-07-23 15:08:34 UTC

SIGit v2.0.5 released - fixes an issue where SIGit data (30078) can get caught in a signing loop.
Also renames some of the exported files to use bech 32 npubs instead of hex keys to make them easier to (manually) verify
https://git.nostrdev.com/sigit/sigit.io/releases

2025-07-20 10:45:24 UTC

v2.0.4 is now released - mostly minor refactoring, but we also made each sigit id partially visible so you can tell when signing 30078 requests, which sigit they relate to
sigit ids are a hash of the create event id and the user npub, so it is not possible to correlate events as an outside observer

2025-07-18 09:07:20 UTC

v2.03 now released with a bunch of improvements to the OTS generation process
Timestamps are generated for the create event and each sign event
Each timestamp has 3 states - pending, upgraded, verified
https://sigit.io

2025-07-16 21:38:47 UTC

v2.02 is released - fixes an issue where the last remaining pdf in a draft sigit could not be deleted, and applies some client side logic to handle the case where relays sometimes do not send an EOSE message
https://sigit.io

2025-07-15 13:56:28 UTC

v02.01 now released - this disables the broadcast button when verifying unencrypted SIGits without signing in
https://git.nostrdev.com/sigit/sigit.io/releases

2025-07-14 18:32:37 UTC

We now have v2 of https://sigit.io !
It was a complete refactor and breaking change, so if you have sigits from the old version you will need to visit the archive version of the site (in top bar)
We'd now like to invite some intrepid users to try the service whilst we smoothen out the rough edges
You can send us feedback here on Nostr, or get in touch to join our power users community

2025-07-10 10:18:16 UTC

Are you interested in helping us test SIGit?
Get early acess to new features and help define the feature roadmap?
We'd love to hear from / involve you.

2025-07-07 16:02:09 UTC

Yes we've been quiet lately - with a big refactor in process
And we just hit commit #1000
Watch this space
https://blossom.sigit.io/a28771aa4933231cba76bc13bc50297256e4eb291a26e68d147ddea29b214ab4.jpeg

2025-01-09 17:03:49 UTC

SIGit is a PRIVATE and SECURE document signing service. It uses Nostr and Blossom for comms and (encrypted) file storage
The project has progressed at a slow pace due to a shortage of funding, however we do push updates almost every week.
You can try it out right now and let us know your feedback:
https://sigit.io

2025-01-06 13:46:05 UTC

- reply

Just type `nostr:` then the npub
Eg: `@npub180c…h6w6`

2025-01-02 10:20:04 UTC

- reply

Great feedback - yeah that's not working right now but we'll fix it for the MVP!
Here's the issue: https://git.nostrdev.com/sigit/sigit.io/issues/297

2025-01-02 10:19:04 UTC

- reply

For some reason we didn't get this notification! For info - we don't rely on (or push) public relays, we use the relays defined by the user (extension / nip-05 / kind 10002) plus the app-relay (sigit relay unless self-hosting and self-adjusted).

2024-12-01 13:08:11 UTC

- reply

Clients (like ours) can and do encrypt content before pushing to blossom though

2024-11-29 13:54:32 UTC

- reply

If only there was a better way..

2024-11-26 23:45:39 UTC

- reply

We expect to come out of beta in Q1 or so

2024-11-26 13:01:26 UTC

- reply

We encrypt and store pdf files on Blossom

2024-11-08 08:04:14 UTC

- reply

Simplex

2024-10-24 11:37:10 UTC

- reply

SIGit
Secure and Private Agreements
https://git.nostrdev.com/sigit/sigit.io

2024-10-09 14:16:24 UTC

- reply

To give feedback, send a DM or talk to us on https://chat.nostrdev.com
Big thanks to @npub1w8l…94qr for the event

2024-10-09 14:13:42 UTC

SIGit was officially (BETA) released today at the Nostr Hack day in Berlin!
https://slides.sigit.io/2024berlin

2024-07-14 17:23:20 UTC

- reply

Thanks! Worked like a charm - https://relay.sigit.io

2024-07-14 15:06:57 UTC

Progress on SIGit continues - we recently dropped the following features:
- History (app data, stored on blossom)
- Notifications (sent as gift-wrapped DMs)
- Encrypted decryption keys - no more copy paste for offline flow
We still need to fix the design, the PDF annotations, and some other stability issues - at which point we'll have the MVP
https://git.nostrdev.com/sigit/sigit.io/pulls/116

2024-07-10 10:29:00 UTC

- reply

Is there a guide to getting this into an existing instance? You need to use the CLI presumably? https://github.com/sebdeveloper6952/strfry-cloudron

2024-07-10 10:25:42 UTC

- reply

We self host gitea - https://git.nostrdev.com
Available on cloudron
Hopefully someone will build a nostr auth plugin soon

2024-07-10 10:08:37 UTC

- reply

done: https://git.nostrdev.com/sigit/sigit.io/commit/d5c45902b8c7f6b36fec10f53d8638c9f24c6bdc

2024-06-28 17:27:12 UTC

- reply

Vamos

2024-06-20 12:13:31 UTC

- reply

https://github.com/lez/nsite
you can literally follow the readme and be live on nostr.hu in just a few minutes!

2024-06-20 10:26:54 UTC

SIGit is now available as an nSite
https://npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq.nostr.hu/#/
#soveng

2024-06-18 22:03:13 UTC

- reply

Nice, thanks for setting this up!

2024-06-14 21:19:37 UTC

- reply

It's super basic.. We'll open source it anyway though, next week, in case anyone would like to use it
https://nostrdev.com

2024-06-13 17:23:56 UTC

- reply

We do
We will, if nobody beats us to it

2024-06-12 14:33:07 UTC

- reply

ready
https://nostrdev.com

2024-06-12 09:24:57 UTC

- reply

We're literally working on this right now! Also the Lorum Ipsum. Ready in a few hours

2024-06-01 06:38:58 UTC

- reply

The domain part (nostr.hu) can be switched out, just like a blossom server
Static sites, with file index (path -> blossom hash) saved as nostr events, served from backend according to npub in subdomain
Could possibly be entirely frontend if served in an iframe

2024-05-29 12:57:21 UTC

Relay Management now available
https://image.nostr.build/91003cb4e7823fe49a5c398d5110688bd8d6d6170a98c338c9778b431de64a5d.png

2024-05-24 23:29:27 UTC

- reply

Have a great time!
We still have one more ticket up for grabs.

2024-05-24 13:02:45 UTC

- reply

check your DM

2024-05-24 12:06:04 UTC

- reply

@npub1ua6…h6v6 ?

2024-05-24 12:05:48 UTC

We have 2 tickets to Adopting Bitcoin available (tomorrow in Arnhem)
Free to anyone building on Nostr - just share your project below

2024-05-17 19:01:42 UTC

- reply

Funchal

2024-05-17 10:48:08 UTC

- reply

We won't support signing in with npubs, to protect user privacy
We're adding a create account feature though

2024-05-17 10:47:12 UTC

- reply

Issue closed. FYI, this signature flow will change in the coming days, but we will continue the use of npubs.

2024-05-15 16:48:57 UTC

- reply

great feedback, thanks! issue raised: https://git.sigit.io/sig/it/issues/40

2024-05-13 16:55:25 UTC

- reply

a machine could be hosting multiple relays, switching according to hostname
in general though the approach sounds good

2024-05-13 16:44:51 UTC

- reply

Depends, the IP could just be a reverse proxy

2024-05-09 08:53:07 UTC

With Nostr, thanks to projects like this, YOU can control your keys!
https://github.com/blackcoffeexbt/hardware-nostr-connect-device

2024-05-07 14:37:08 UTC

- reply

Hi Karnage!
We would really love your advice / input
Could we send you the poc link at the end of the week, once we smooth the rough edges?

2024-05-07 14:36:54 UTC

- reply

DM'd!

2024-05-06 21:59:27 UTC

- reply

This: https://fedibtc.github.io/fedi-docs/docs/mods/intro

2024-05-06 21:56:21 UTC

- reply

Actually we're not fedi-ready (yet) but when fedi (the app) is ready we'd like to include SIGit as a homescreen Mod

2024-05-06 21:10:37 UTC

- reply

Be great to discuss how our client-centric design prevents anyone (including us) from spying on users

2024-05-06 20:37:15 UTC

- reply

We'd love to!
See you there

2024-05-06 20:04:51 UTC

Working on a free and open source document signing tool (PWA)
Nostr for network and identity, Blossom for storage (encrypted content)
Self hostable / fedi-ready
We have a functional PoC, but it needs a little design love..
Anyone available for a conversation?
#nostrdesign #soveng

2024-05-02 11:17:17 UTC

- reply

it wouldn't be available for "all profiles" if the latter.
Maybe a two pronged approach..
"First seen: "
"Confirmed:"

2024-05-02 11:14:07 UTC

- reply

@npub1der…xzpc - should it be the created_at of the earliest found event, or should one instead scan only for NIP-03 timestamped events?

2024-05-02 10:45:54 UTC

- reply

#comingsoon
https://git.sigit.io/sig/it/issues/1

2024-05-01 08:27:41 UTC

- reply

See you in June!

2024-04-21 20:14:05 UTC

#sigit now has colour coded profiles based on the first 6 chars of the hex of the pubkey
This helps to guard against fake accounts
@npub1ye5…knpr
#soveng
https://image.nostr.build/28f077a8fa3ee46fda583f473900771be635c245deef393c90c8ba6b9c3d3711.jpg

2024-04-16 16:12:03 UTC

- reply

would be nice to be able to easily configure the defaults for new accounts, eg relay lists / kind 0 attributes
password reset (and change) is also a biggy. perhaps a secondary nostr account could be used as a fallback instead of email?

2024-04-15 18:16:21 UTC

SIGit is a decentralised document signing tool
The base product will be free and FOSS
https://git.sigit.io
#soveng #sigit

2024-04-15 18:13:25 UTC

Currently building on NIP-65 to ensure decentralised message deliverability on SIGit