Desktop key vault for apelido and brisa: signs handles, powers of attorney, gov.br attestations, key rotations and claims, with private keys that never leave it
  • JavaScript 50.9%
  • Go 40.8%
  • Java 3.3%
  • HTML 2.2%
  • CSS 2%
  • Other 0.8%
Find a file
Ruben M. Damião f4407fee94 an app is given what its code asks for, one power of attorney per protocol
apelido's grants have a scope now. GrantWithCode gives one grant for each
protocol the access code names, taking back first what the app already
holds of them; Grant, for another device, still gives the one over
everything. The vault records the protocols of each grant, Revoke takes
back every one it gave, and Check counts an attorney as holding when the
chain has them all (KeyFor asks the node of one protocol's grant).

The request page and the account's list say in words what a yes gives or
gave, and warn when an app asks for everything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 18:23:48 -03:00
android android: an app beside the Crachá is let in without the chain 2026-10-07 23:54:30 -03:00
cmd an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
frontend an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
mobile android: a fingerprint in place of the password, and the vault locked off the screen 2026-10-07 23:49:53 -03:00
ui an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
.gitignore crachá: your identity, kept with you 2026-09-29 22:17:57 -03:00
cracha-web cracha-web: Crachá hosted 2026-10-01 23:50:29 -03:00
cracha.go an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
cracha_test.go an app's access code, and the network from apelido/rede 2026-10-01 00:31:59 -03:00
device.go crachá: your identity, kept with you 2026-09-29 22:17:57 -03:00
entrar.go android: an app beside the Crachá is let in without the chain 2026-10-07 23:54:30 -03:00
entrar_test.go android: an app beside the Crachá is let in without the chain 2026-10-07 23:54:30 -03:00
go.mod the recovery code from one Crachá to another by QR 2026-10-07 21:27:03 -03:00
go.sum the recovery code from one Crachá to another by QR 2026-10-07 21:27:03 -03:00
govbr.go crachá: your identity, kept with you 2026-09-29 22:17:57 -03:00
install.sh install.sh: the desktop Crachá as an app of the desktop 2026-10-05 21:20:24 -03:00
interest_test.go the vault's own part of the chain: kept, asked of relays, and the network come configured 2026-10-06 23:18:33 -03:00
kept.go the vault's own part of the chain: kept, asked of relays, and the network come configured 2026-10-06 23:18:33 -03:00
kept_test.go the vault's own part of the chain: kept, asked of relays, and the network come configured 2026-10-06 23:18:33 -03:00
network.go crachá: your identity, kept with you 2026-09-29 22:17:57 -03:00
palcos.go the vault's own part of the chain: kept, asked of relays, and the network come configured 2026-10-06 23:18:33 -03:00
palcos_test.go follow rede: a block has no Source 2026-10-01 01:30:43 -03:00
proof.go crachá: your identity, kept with you 2026-09-29 22:17:57 -03:00
queries.go an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
scope_test.go an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
seed.go an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00
seed_test.go stages, a recovery code, and the wallet's balance 2026-09-30 01:49:28 -03:00
socket.go an app's access code, and the network from apelido/rede 2026-10-01 00:31:59 -03:00
testnet_test.go stages, a recovery code, and the wallet's balance 2026-09-30 01:49:28 -03:00
vault.go an app is given what its code asks for, one power of attorney per protocol 2026-10-09 18:23:48 -03:00