Simplex


SIGit

Secure and Private Agreements

https://git.nostrdev.com/sigit/sigit.io


To give feedback, send a DM or talk to us on https://chat.nostrdev.com

Big thanks to nostr:npub1w8lxsgc67y5jmvgfhjqrxtkj0gnxtrcsvrtzh97kpd66pw35e5gstn94qr  for the event


SIGit was officially (BETA) released today at the Nostr Hack day in Berlin!

https://slides.sigit.io/2024berlin


SIGit

Secure & Private Agreements

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


"SIGit"


"Secure & Private Agreements\n\nAn open-source, self-hostable solution for secure document signing and verification."


# 🚀 Nostr Hackday Agenda Announcement 🚀

Join us for an exciting day of collaboration, learning, and hacking with a diverse group of Nostr enthusiasts and developers!

## Schedule Highlights:

- 9:00 - 10:00: Breakfast + Coffee @c-base
- 10:00 - 10:30: 1-minute project intros
- 10:30 - 12:30: Project presentations (satshoot, sigit, shopstr, electrum)
- 13:00 - 14:00: Lunch (Pizza thanks to Fedi)
- 14:00 - 14:30: TollGate setup
- 15:00 - 17:00: Attendee-led unconference
- 17:00 - 17:30: Gathering outcomes
- 19:00 - 22:00: Socratic seminar (bitdevs.berlin/)

## What to Expect:

- Chance to demo your projects and get feedback from the community
- Network with fellow Nostr developers and enthusiasts
- Ideate on new Nostr-based applications and services
- Explore potential solutions for onboarding newcomers
- Discussions on best practices and innovative hacks
- Share and learn about exciting projects like SatShoot.com, Shopstr, njump.me, amethyst and more
- Opportunities for pair programming, building on hacker badges and collaborative problem-solving

Whether you're a seasoned Bitcoin developer, a Nostr newbie, or somewhere in between, there's something for everyone at this Hackday!

Don't miss this opportunity to connect, contribute, and shape the future of Nostr!


How does Ledger know how much bitcoin their devices secure? 🤔🤔🤔


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


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


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


We self host gitea - https://git.nostrdev.com

Available on cloudron

Hopefully someone will build a nostr auth plugin soon


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


Vamos


https://github.com/lez/nsite

you can literally follow the readme and be live on nostr.hu in just a few minutes!


SIGit is now available as an nSite

https://npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq.nostr.hu/#/

#soveng


We're here to help YOU build your Nostr product or idea!

#introductions

#nostr

https://nostrdev.com


Nice, thanks for setting this up!


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

https://nostrdev.com


We do

We will, if nobody beats us to it


We are organizing a nostr hack day in Berlin on the 9th of October. Later that evening there will be a [Socratic seminar]( https://bitdevs.berlin/ ) and [BTC++]( https://btcplusplus.dev/conf/berlin24 ) will start the next day.

Some of the workshops include:

Sigit:
nostr:npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq

Shopstr: nostr:npub15dc33fyg3cpd9r58vlqge2hh8dy6hkkrjxkhluv2xpyfreqkmsesesyv6e

Git remote nostr:
https://github.com/lez/git-remote-nostr

Satshoot:
https://github.com/Pleb5/satshoot

And TollGate:
https://github.com/chGoodchild/GLTollGate

Feel free to reach out if you have something you would like to present!


ready

https://nostrdev.com


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


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


Relay Management now available

 https://image.nostr.build/91003cb4e7823fe49a5c398d5110688bd8d6d6170a98c338c9778b431de64a5d.png


Have a great time!

We still have one more ticket up for grabs.


check your DM


nostr:npub1ua6fxn9ktc4jncanf79jzvklgjftcdrt5etverwzzg0lgpmg3hsq2gh6v6 ?


We have 2 tickets to Adopting Bitcoin available (tomorrow in Arnhem)

Free to anyone building on Nostr - just share your project below


BTC Prague dev/hack/day – this could be its own 2-day conference with fewer parallel tracks.

🔥

https://m.primal.net/IJup.png


Funchal


We won't support signing in with npubs, to protect user privacy

We're adding a create account feature though


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


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


A ratchet can only turn in one direction.

The double ratchet means two types of ratchets: a KDF ratchet (the small ratchet in the diagram) and a DH ratchet (the large ratchet in the diagram).

KDF stands for Key Derivation Function. A hash function is the simplest KDF because it is one-way. K1=hash(K0), K2=hash(K1), K3=hash(K2), K4=hash(K3)... K1 is used to encrypt the first message, K2 to encrypt the second message, and so on. Once used, the key is deleted. If an attacker obtains the latest encryption key K5, they cannot reverse-engineer K4, K3, K2, or K1, ensuring the security of historical messages. Thus, the KDF provides forward secrecy to the encryption protocol.

However, the attacker can derive K6, K7, K8..., which means there is no backward secrecy. This is where the DH ratchet comes into play.

The Diffie–Hellman (DH) key exchange is a mathematical method for securely exchanging cryptographic keys over a public channel. Alice, using her private key S1 and Bob’s public key P2, can compute a value. Similarly, Bob, using his private key S2 and Alice’s public key P1, can compute a value. These two values are equal.

Alice and Bob continuously generate new DH key pairs for new messages on the client side and attach the public key in plaintext to the message. The message recipient can then use this public key and their private key to perform the DH computation. This DH ratchet effectively resets the KDF ratchet with the DH ratchet. Because the attacker does not know the latest DH private key, they cannot derive future encryption keys, thus providing backward secrecy.

Therefore, in the double ratchet algorithm, the KDF ratchet ensures forward secrecy, and the DH ratchet ensures backward secrecy, together achieving both forward and backward secrecy.

We recommend the following video, which provides a more intuitive animation demonstration.

https://youtu.be/9sO2qdTci-s?si=BXLU33BRANWAJKMz

https://youtu.be/7uEeE3TUqmU?si=jpPOR_O61IppgJxl

(We hope users can understand the basic principles to judge for themselves which chat applications are good.) https://image.nostr.build/02cf8185e461b3ce03d84397debf4901724f5ed4d1198f83913fa2303e3a0214.png  nostr:note1ffgsgvkltl96wzwe6lakv2ntjfkq2u48msx57mrvnnhtyde5s2js8antlr


a machine could be hosting multiple relays, switching according to hostname

in general though the approach sounds good


Depends, the IP could just be a reverse proxy


With Nostr, thanks to projects like this, YOU can control your keys!

https://github.com/blackcoffeexbt/hardware-nostr-connect-device


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?


DM'd!


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


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


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


We'd love to!

See you there


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


it wouldn't be available for "all profiles" if the latter.

Maybe a two pronged approach..

"First seen: "
"Confirmed:"


nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc - should it be the created_at of the earliest found event, or should one instead scan only for NIP-03 timestamped events?


#comingsoon

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


See you in June!


#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

nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

#soveng
 https://image.nostr.build/28f077a8fa3ee46fda583f473900771be635c245deef393c90c8ba6b9c3d3711.jpg


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?


SIGit is a decentralised document signing tool

The base product will be free and FOSS

https://git.sigit.io

#soveng #sigit


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