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!

Last month we scored a podium finish at the Baltic Honeybadger 2025 Hackathon for @nprofile1q..., sponsored by @nprofile1q... and with funds distributed through @nprofile1q...

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

@nprofile1q...

@nprofile1q...

@nprofile1q...

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

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.

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

On-boarding to @nprofile1q... 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

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

We are participating in the HoneyBadger Hackathon, sponsored by Angor!

Below is our first ever demo video

#BH2025

https://vid.ft.hn/w/oWTfZdMapZdxwdwJQTspdk

@nprofile1q..., fyi

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

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