enes
235e76be4e
All checks were successful
Release to Staging / build_and_release (push) Successful in 1m16s
This change will potentially close multiple issues related to the gift-wrapped events processing (#168, #158). Further testing will be required to confirm before closing each. The commented-out code causes the race condition during the processing of the gift wraps with sigits. During the processing we perform checks to see if sigit is outdated. In cases where sigit includes multiple signers it's possible for a signer to receive multiple sigit updates at once (especially noticeable for 3rd, 4th signer). Due to async nature of processing we can have same sigit enter processing flow with different states. Since this code also updates user's app state, which includes uploads to the blossom server it takes time to upload local user state which causes both to check against the stale data and un-updated app state. This results in both sigits being "new" and both proceed to update user state and upload app data. We have no guarantees as in which event will update last, meaning that the final state we end up with could be already stale. The issue is also complicated due to the fact that we mark the gift wraps as processed and it's impossible to update the state without creating a new gift wrap with correct state and processing it last to overwrite stale state. This is temporary solution to stop broken sigit states until proper async implementation is ready. Co-authored-by: b Reviewed-on: #193 Reviewed-by: eugene <eugene@nostrdev.com> Co-authored-by: enes <mulahasanovic@outlook.com> Co-committed-by: enes <mulahasanovic@outlook.com> |
||
|---|---|---|
| .git-hooks | ||
| .gitea/workflows | ||
| public | ||
| src | ||
| .env.example | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .prettierrc | ||
| contributing.md | ||
| index.html | ||
| LICENSE | ||
| licenseChecker.cjs | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
SIGit
SIGit is a decentralised document signing tool, currently under active development. Document Signing is a $30 billion industry yet has two major structural flaws:
- Your signing provider can read ALL your documents (and even use them to train their proprietary AI)
- Your signatories do not own their keys (cloud email and/or SMS are not secure)
The trouble, of course, is all the trust that is required to make things work.
SIGit is a signing technology that is more secure and private than any off-the-shelf self-hosted or SaaS based solution. This is a result of two design factors:
- The use of NOSTR for identity and key management (not your keys, not your signature)
- Encryption of documents at every stage (we have no idea what you are signing)
Of course, being built on the Nostr relay network, you can sign documents and build business relationships even in the most adversarial of regulatory environments.
The source for this repo is: https://git.sigit.io/sig/it
If you'd like to submit PRs or issues (which are very welcome) please reach out by DM for an invite to the source repo: https://njump.me/npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq
We expect to have an MVP by the summer, if you are interested in being an early tester, do reach out on https://chat.sigit.io