issues
search
rodentrabies
/
bp
Bitcoin Protocol components in Common Lisp
MIT License
37
stars
8
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Switch from cffi libsecp256k1 to ironclad secp256k1
#15
kilianmh
opened
2 months ago
1
meta: use dots instead of slashes in qualified package names
#14
rodentrabies
closed
1 year ago
0
tests: use property based tests on encoding/decoding
#13
Titan-C
closed
1 year ago
0
crypto: expose secp256k1 `combine-pubkeys`
#12
Titan-C
closed
1 year ago
2
crypto: fix expected argument type in `serialize-pubkey`
#11
Titan-C
closed
1 year ago
1
meta: introduce dot-separated package nicknames
#10
rodentrabies
closed
1 year ago
1
Fix various stylistic issues
#9
kilianmh
opened
2 years ago
0
Implement Bech32/Bech32m encoding/decoding
#8
rodentrabies
closed
3 years ago
0
Rewrite README.md from GFM to Org
#7
rodentrabies
closed
3 years ago
0
Not an issue, just a comment
#6
jccerrillo
closed
3 years ago
1
Initial network layer implementation
#5
rodentrabies
closed
4 years ago
0
Coinbase transaction validation
#4
rodentrabies
closed
4 years ago
0
Package-lock-related Travis CI failures
#3
rodentrabies
closed
4 years ago
0
Investigate Lisp implementations failing the CI
#2
rodentrabies
opened
4 years ago
0
Less verbose opcode definition
#1
rodentrabies
opened
4 years ago
0