mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity
master
lightning-bolts/.aspell.en.pws

439 lines
3.7 KiB
Plaintext
Raw Permalink Normal View History

make spellcheck.sh happy
2017-11-14 04:18:09 +01:00
personal_ws-1.1 en 264
BOLT7: query_short_channel_ids: allow requesting specific information (folded) Nodes can append additional data to their `query_short_channel_ids` messages, which consists in one flag per short channel id and specifies what they would like to receive (`node_announcement`, `channel_announcement`, or/and one `channel_update` or both).
2019-07-17 09:21:14 +02:00
bitfields
checksums
timestamps
tlv
Spelling fixes
2019-07-22 19:00:30 +02:00
tlvs
subtype
BOLT7: query_short_channel_ids: allow requesting specific information (folded) Nodes can append additional data to their `query_short_channel_ids` messages, which consists in one flag per short channel id and specifies what they would like to receive (`node_announcement`, `channel_announcement`, or/and one `channel_update` or both).
2019-07-17 09:21:14 +02:00
TLV
spelling: check all the .md files Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-07-19 08:06:23 +02:00
py
vsprintf
glibc
JSON
Freenode
nacks
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
secp
sig
unguessable
libsecp
TCP
DER
micropayments
nhops
retransmitted
dev
tradeoff
interactive-tx: Add dual-funding flow, using the interactive tx protocol This commit adds the interactive transaction construction protcol, as well as the first practical example of using it, v2 of channel establishment. Note that for v2 we also update the channel_id, which now uses the hash of the revocation_basepoints. We move away from using the funding transaction id, as the introduction of RBF* makes it such that a single channel may have many funding transaction id's over the course of its lifetime. *Later, also splicing
2021-03-03 04:10:33 +01:00
kiloweight
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
mixHeader
uint
hopsData
bitfield
B'th
decrypting
rhokey
rhoKey
buf
millisatoshis
yToX
funder's
IRATEMONK
wpkh
nextHmac
basepoint
streamKey
Spelling list: add new words. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-06 02:12:33 +01:00
localpubkey
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
paymentPath
SPV
HopData
CSV
xFFFFFFFFFF
plaintext
EQUALVERIFY
AEAD
secretkey
TripleDH
addr
CHECKMULTISIG
decryptWithAD
routable
epk
scriptpubkey
mukey
muKey
sharedSecretSize
DUP
sharedSecrets
xFFFFFFFFFFFF
cryptographic
generateSharedSecret
instantiations
deterministically
deduplication
FIPS
responder
UTF
blockchain
Add bolt11 test vector with amount in `p` units (#699)
2020-03-03 18:36:44 +01:00
Blockstream
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
nSequence
decrypt
flen
incrementing
feerate
affine
CHECKSEQUENCEVERIFY
nonces
iff
serializeCompressed
prepended
roasbeef
multisig
nodepk
remotesig
hopBlindingFactors
ECDH
addrlen
assocData
ActOne
ammag
computeBlindingFactor
wsh
multiScalarMult
BOLT 2: typo fixes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 08:48:01 +02:00
onionpacket
tools/spellcheck: add modern words to our dict (Travis is old) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 09:34:53 +02:00
OnionPacket
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
ikm
fillerSize
txinput
init
reconnection
milli
revocationsig
NOTIF
generateHeaderPadding
IPv
ipv
satoshi
delayedsig
hopDataSize
I'th
segwit
interactive-tx: Add dual-funding flow, using the interactive tx protocol This commit adds the interactive transaction construction protcol, as well as the first practical example of using it, v2 of channel establishment. Note that for v2 we also update the channel_id, which now uses the hash of the revocation_basepoints. We move away from using the funding transaction id, as the introduction of RBF* makes it such that a single channel may have many funding transaction id's over the course of its lifetime. *Later, also splicing
2021-03-03 04:10:33 +01:00
RBF
accepter
accepter's
subtype
redeemScript
scriptSig
utxo
scriptPubKey
scriptPubKeys
scriptlen
sats
BOLT 2: typo fixes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 08:48:01 +02:00
htlc
BOLT 7,11: Added an optional `min_final_cltv_expiry` field in BOLT 11 (#258) Added an optional `c` field in the payment request specifying the minimum `cltv_expiry` to use for the last htlc in the route. If not provided, default value is 9. This commit also clarifies how `channel_update` messages are only to be used in the context of relaying payments, and how both htlc amounts and expiries are to be calculated backwards from the values provided in the payment request. Not needing the `channel_update` for the first channel in a route also means that it is possible to make a payment through a channel which hasn't had any announcements yet.
2017-10-18 15:31:31 +02:00
htlcs
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
ChaCha
len
ciphertext
endian
C'mon
NewOnionPacket
keypair
preimage
MiTM
mempool
cltv
localfeatures
iteratively
PrivateKey
br
millisatoshi
trustless
ee
eg
hopSize
retransmit
BOLT 0,2: update stylesheet, apply associated changes, 2nd pass copy-edit BOLT 0: Update style sheet to reflect correct Bitcoin capitalizations BOLT 2: Complete second pass copy-edit according to stylesheet guidelines
2017-11-18 21:00:36 +01:00
retransmittal
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
deobfuscating
onchain
BADONION
rightShift
protocolName
hopEphemeralPubKeys
txid
Fn
PublicKey
tools/spellcheck.sh: add --check option, add tests to travis. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 09:25:02 +02:00
encryptWithAD
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
liveness
ie
shakin
txin
globalfeatures
calcMac
privkey
overpayment
hopSharedSecrets
TimeLocked
timelocked
lc
btcec
localsig
responder's
ripemd
md
ENDIF
blockchains
cleartext
streamBytes
WISTFULTOLL
locktime
xFFF
localprivkey
deserialized
pubkey
PubKey
ok
Retransmissions
numHops
failuremsg
BOLT 1: misc typo fixes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 08:47:06 +02:00
fundee
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
byteslen
shortid
se
rk
micropayment
rn
testbit
unparsable
sk
RoutingInfo
funder
Counterintuitively
decrypts
sn
generateFiller
unrevoked
ss
that'd
ack
deobfuscated
gflen
satoshis
instantiation
HeaderMAC
blindGroupElement
tx
pubkeys
CHECKLOCKTIMEVERIFY
tools: Add CLTV acronyms
2017-07-11 12:32:59 +02:00
CLTV
CLTVs
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
generateCipherStream
XK
lflen
deobfuscates
generateKey
alice
revocationprivkey
PKH
Spelling list: add new words. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-06 02:12:33 +01:00
remotepubkey
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
HKDF
ooo
repo
num
numStreamBytes
txout
HTLCs
make spellcheck.sh happy
2017-11-14 04:18:09 +01:00
HTLC's
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
retransmission
decrypted
BOLT 2: typo fixes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 08:48:01 +02:00
sessionKey
tools/spellcheck: add modern words to our dict (Travis is old) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 09:34:53 +02:00
sessionkey
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
routingInfoSize
hostname
rgb
ciphertexts
BOLT 3: typo fixes. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 08:59:04 +02:00
wscript
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
CHECKSIG
pre
numMaxHops
HMACs
hmac
BIP
hmacSize
ratelimit
talkin
Spelling list: add new words. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-06 02:12:33 +01:00
revocationpubkey
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
msat
func
unencrypted
coinbase
priv
sha
TODO
ChaChaPoly
Spelling list: add new words. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-06 02:12:33 +01:00
delayedpubkey
Add spellcheck tool (requires `aspell`), also spellcheck. This is a multi-part message in MIME format. This patch should apply to http://github.com/lightningnetwork/lightning-rfc Nonidealities: Aspell triggers spelling errors on the hexadecimal strings in the test vectors. I don't have enough aspell-fu to figure out how to make Aspell ignore these. There are 2 possible pluralizations of `HTLC`: `HTLCs` and `HTLC's`. I'd prefer the latter, but for now I support both. We should standardize pluralization; we can edit the `.aspell.en.pws` file to remove the pluralization we won't choose.
2017-04-29 05:19:07 +02:00
Diffie
IETF
xFFFFFFFFFFF
FIXME
EphemeralKey
tools/spellcheck: add modern words to our dict (Travis is old) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-02 09:34:53 +02:00
bitcoin
Bitcoin
smartphone
other's
remote's
multi
bitcoin's
IP
aa
df
versa
timestamp
metadata
Bitcoin's
Versioning
aspell: Make CI happy again
2017-05-16 13:43:12 +02:00
checksum
tools/spellcheck: expiries is a valid word. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-19 03:27:36 +02:00
expiries
Bolt 11: Invoice Protocol for Lightning Payments (#183) This specifies a draft invoice protocol for lightning payments. Particular thanks for detailed feedback from: * ZmnSCPxj <ZmnSCPxj@protonmail.com> * @Saicere * @kallewoof * @halseth * @cdecker Signed-off-by: Rusty Russell <rusty@blockstream.com>
2017-06-27 12:38:13 +02:00
bech
Bech
nano
pico
mainnet
testnet
icecream
spelling: fix spelling mistakes + add new words to ignore spelling
2023-11-02 20:16:53 +01:00
extractable
de
anonymize
Punycode
rck
sck
zeroconf
Bolt 11: Invoice Protocol for Lightning Payments (#183) This specifies a draft invoice protocol for lightning payments. Particular thanks for detailed feedback from: * ZmnSCPxj <ZmnSCPxj@protonmail.com> * @Saicere * @kallewoof * @halseth * @cdecker Signed-off-by: Rusty Russell <rusty@blockstream.com>
2017-06-27 12:38:13 +02:00
swiss
lollypop
UTC
inline
BOLT 2: channel_reestablish message, retransmission simplification. This adds a message for each channel reconnect (after we've sent/received `funding_signed`, ie. when we rememeber the channel), which says exactly how many `commitment_signed` and `revoke_and_ack` we've received. Really, we could use one bit for each (they could only be missing the last one), but better to be clear. This leaves the "rollback if didn't get commitment_signed" requirement, but avoids any need to handle update duplicates or wonder what update number a `commitment_signed` applies to after reconnect. Many thanks to pm47 and roasbeef especially for constructive feedback which made this far better than I originally had. Closes: #172 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-24 07:42:18 +02:00
fundee's
tools: Add CLTV acronyms
2017-07-11 12:32:59 +02:00
BOLTs
bolt10: shutting the spellchecker up once more
2017-08-12 19:51:56 +02:00
DNS
subdomain
subdomains
wildcard
tuple
tuples
resolvers
hostnames
prepending
A
AAAA
SRV
TTL
BOLT 11: recommend URI schemes. This is unofficial, since we don't have IANA tag, but it doesn't clash with any existing one. We'll see if this turns out to be something people want. Closes: #206 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-08-21 06:49:23 +02:00
URI
Typo fix: CTLV -> CLTV. Locktime, not timelock. Found this in my code, too, so pretty sure it's my fault! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-10-03 03:41:29 +02:00
cli
htlckey: new basepoint avoid holding the payment secret. This is stolen from @sstone's #243 "reduce attack surface". This breaks compatibility, as agreed at the 2017-11-13 meeting. Note also that it does not update the test vectors. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-10-31 02:02:32 +01:00
paymentkey
Spelling list: add new words. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-06 02:12:33 +01:00
htlcpubkey
htlckey: new basepoint avoid holding the payment secret. This is stolen from @sstone's #243 "reduce attack surface". This breaks compatibility, as agreed at the 2017-11-13 meeting. Note also that it does not update the test vectors. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-10-31 02:02:32 +01:00
remotehtlcsig
localhtlcsig
basepoints
Appended Bitcoins to word list
2017-11-28 00:01:19 +01:00
Bitcoins
make spellcheck happy
2017-12-19 02:16:26 +01:00
bitcoins
make spell check happy
2017-12-04 02:26:32 +01:00
deobfuscate
Manual rebase of Shannon's PR-294 rewrite. This got a little messy as some changes now needed to be applied in two places, and other wording has been completely removed. Another pass on top will be required. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-12-06 07:08:32 +01:00
offerer
offerer's
spelling: add incentivize to dictionary. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-12-18 20:10:12 +01:00
incentivize
make spellcheck happy
2017-12-19 07:41:19 +01:00
redemptions
BOLT 2: clarify that feerate is in *satoshi* per ksipa. We don't actually say that! Closes: #336 Reported-by: Matt Corallo Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-12-21 05:12:00 +01:00
vbytes
spell: Add BTC acronym to dictionary
2018-01-13 18:15:25 +01:00
BTC
Add bolt11 test vector with amount in `p` units (#699)
2020-03-03 18:36:44 +01:00
USD
aspell: adds injection attack keywords to dictionary * javascript * Javascript * DOM * SQL * XSS * Implementers * sanitization
2018-01-09 01:28:54 +01:00
XSS
SQL
DOM
Javascript
javascript
Implementers
sanitization
BOLT 4: Clarify the onion construction section. The new description introduces the concept of an ephemeral private key, which I find easier to reason about and suggests a linear instead of quadratic construction algorithm.
2018-02-04 09:18:16 +01:00
ek
reblind
BOLT 4: Update onion construction reference code. The description now suggests the use of an ephemeral private key, so the reference code is simplified by using that concept. The reference code is also updated to make fewer calls to undefined functions.
2018-02-04 09:53:37 +01:00
ephemeralKey
ephemeralPrivKey
ephemeralPubKey
ecdhResult
scalarMult
blindingFactor
Mul
add the word 'regtest' to the spellchecker
2018-03-20 16:06:22 +01:00
unlinkable
regtest
BOLT 7: query_messages option. [ This was a joint effort by many people, with iterations not indicated in this final commit: thanks to all who reviewed and polished! Particularly: @jimpo @cdecker @sstone @ZmnSCPxj ] This enables three new functions: 1. query_short_channel_ids: they will send channel_announcement / channel_update / node_announcement followed by reply_short_channel_ids_done. 2. query_channel_range: they will send one or more reply_channel_range with the short_channel_ids in these blocks. 3. gossip_timestamp_filter: filters what gossip they send. It also changes behavior: we no longer send a `channel_announcement` until we have at least one `channel_update`. The announcement is fairly useless without an update already, but this in particular enables reasonable timestamp filtering (channel_announcement does not have an explicit timestamp). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-06-26 23:02:11 +02:00
ratelimiting
BOLT 7: Add compressed (zlib) encoding. [ Note: in retrospect, adding this in the initial draft without its own feature bit was a mistake. It was a premature optimization, adds complexity and removes the ability to disable it if a problem is found without disabling gossip_queries entirely. However, it is already deployed as-is. --RR ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-06-26 23:05:15 +02:00
zlib
ZLIB
BOLT 2: add missing spellcheck words, change 'funding txo' to 'funding output'. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-11-29 05:30:38 +01:00
APIs
duplicative
BOLT7: query_short_channel_ids: allow requesting specific information (folded) Nodes can append additional data to their `query_short_channel_ids` messages, which consists in one flag per short channel id and specifies what they would like to receive (`node_announcement`, `channel_announcement`, or/and one `channel_update` or both).
2019-07-17 09:21:14 +02:00
CRC
BOLT #7: receiving node requirements related to timestamp for channel_update message (#621) Clarify timestamp requirements for channel_update messages.
2019-07-16 09:24:26 +02:00
DoS
ECDSA
BOLT01: add TLV spec
2019-04-30 04:35:56 +02:00
TLV
bolt04: Shut the spellchecker up
2019-06-06 21:39:48 +02:00
tlv
BOLT01: add TLV spec
2019-04-30 04:35:56 +02:00
namespace
verifier
verifiers
EOF
monotonicity
optimizations
structs
CompactSize
encodings
option_static_remotekey: final draft. This separates out the static remotekey changes from the more ambitious option_simplified_commitment (which also included pushme outputs and bring-your-own-fee for HTLC outputs). As per http://www.erisian.com.au/meetbot/lightning-dev/2019/lightning-dev.2019-09-02-20.06.html Thanks to everyone for feedback: @araspitzu @roasbeef @bitconner Suggested-by: @roasbeef Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-28 09:21:28 +02:00
remotekey
BOLT01: swap CompactSize for BigSize in TLV format This commit modifies the varint encoding used for TLV types and lengths to use a custom format called BigSize. The format is identical to bitcoin's CompactSize, except it replaces the use of little-endian encodings for multi-byte values with big-endian. This is done to prevent mixing endianness within the protocol, since otherwise CompactSize would be the first introduction of little-endian encodings.
2019-07-12 03:22:24 +02:00
bigsize
BigSize
spellcheck: allow space-separated hex, and a few new terms. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-07-16 05:31:13 +02:00
namespaces
tlvs
bolt04: Shut the spellchecker up
2019-06-06 21:39:48 +02:00
fips
rfc
BOLT 9: Add feature bits for payment_secret and basic_mpp. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-11-26 04:13:48 +01:00
multipath
mpp
bolt04: Shut the spellchecker up
2019-06-06 21:39:48 +02:00
tlvs
spelling: check all the .md files Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-07-19 08:06:23 +02:00
snprintf
GitHub
IRC
BOLT 9: flatten feature fields. We simply specify, in each case, where they will appear ("Context"). Because `globalfeatures` is already in use, we fold that into the renamed `localfeatures` field to unify them (now called `features`), but dissuade further use. Note also: we REQUIRE minimal `features` field in channel_announcement, since otherwise both sides of channel will not agree and not be able to create their signatures! Consider these theoretical future features: `opt_dlog_chan`: a new channel type which uses a new discrete log HTLC type, but can't support traditional HTLC: * `init`: presents as odd (optional) or even (if traditional channels not supported) * `node_announcement`: the same as above, so you can seek suitable peers. * `channel_announcement`: presents as even (compulsory), since users need to use the new HTLCs. `opt_wumbochan`: a node which allows channels > 2^24 satoshis: * `init`: presents as odd (optional), or maybe even (if you only want giant channels) * `node_announcement`: the same as above, so you can seek suitable peers. * `channel_announcement`: not present, since size of channel indicates capacity. `opt_wumbohtlc`: a channel which allows HTLCs > 2^32 millisatoshis: * `init`: presents as odd (optional), or even (compulsory) * `node_announcement`: the same as above, so you can seek suitable peers. * `channel_announcement`: odd (optional) since you can use the channel without understanding what this option means. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Co-Authored-By: Bastien Teinturier <31281497+t-bast@users.noreply.github.com>
2019-09-17 07:21:17 +02:00
bitmasks
BOLT-04: modify Sphinx packet construction to use starting random bytes In this commit, we modify the existing instructions to create the Sphinx packet to no longer start out with a zero initialize set of 1366 bytes. Instead, we now instruct the sender to use _random_ bytes derived from a CSPRG. This fixes a recently discovered privacy leak that allows an adversarial exit hop to ascertain a lower bound on the true path length. Note that this doesn't affect packet processing, so this is a backwards compatible change. Only clients need to update in order to avoid this privacy leak. After this change is applied, the test vectors as is don't match the spec, as they're created using the original all zero starting bytes. We can either update these with our specified set of random bytes, or leave them as is, as they're fully deterministic as is. An alternative path would be to generate more random bytes from the shared secret as we do elsewhere (the chacha based CSPRNG).
2019-11-06 03:26:54 +01:00
CSPRNG
Clarify numerical comparison of pubkeys (#743) We are using lexixographic order (which is the same as big-endian when inputs have the same size, such as compressed public keys).
2020-02-18 09:53:12 +01:00
lexicographically
Make explicit witness must conform to MINIMALIF (#764)
2020-04-27 21:50:57 +02:00
MINIMALIF
Anchor outputs This commit extends the specification with a new commitment format that adds two anchor outputs to the commitment transaction. Anchor outputs are a safety feature that allows a channel party to unilaterally increase the fee of the commitment transaction using CPFP and ensure timely confirmation on the chain. There is no cooperation required from the remote party.
2020-08-19 12:29:11 +02:00
SIGHASH
bolt-09: reserve feature bits for option_anchors_zero_fee_htlc_tx (#828)
2021-01-04 20:40:57 +01:00
sighash
Anchor outputs This commit extends the specification with a new commitment format that adds two anchor outputs to the commitment transaction. Anchor outputs are a safety feature that allows a channel party to unilaterally increase the fee of the commitment transaction using CPFP and ensure timely confirmation on the chain. There is no cooperation required from the remote party.
2020-08-19 12:29:11 +02:00
ANYONECANPAY
cpfp
utxo
txes
csv
CHECKSIGVERIFY
IFDUP
sats
BOLT 2: `option_shutdown_anysegwit` In bitcoin 0.19.0, standardness rules are going to be relaxed to allow future witness versions. Once this is widely deployed, it will be safe to accept them, smoothing use of future segwit versions. See: https://github.com/bitcoin/bitcoin/pull/15846 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-18 02:33:03 +02:00
anysegwit
BOLT 2: quiescence protocol. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Header from folded patch 'bolt_2__set_an_initiator_in_quiescence.patch': BOLT #2: Set an initiator in quiescence. This is especially useful for protocols such as splicing; for simplified commitment transactions, there is already an implied initiator at each point, so having the negotiation at splicing time would be redundant. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Header from folded patch 'option_quiesce__feature_to_support_stfu_method.patch': option_quiesce: feature to support stfu method. In practice, sftu is useless unless you have something (e.g. channel_upgrade) which uses it, but adding a feature is best practice IMHO. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2024-06-11 09:44:20 +02:00
quiesce
quiescing
SomeThing
BOLT 4: onion message support. These use onion encoding for simple one-way messaging: there are no error returns. However, every onion uses route blinding *even if it doesn't need to*. You can prove what path was used to reach you by including `path_id` in the encrypted_data_tlv. Note that this doesn't actually define the payload we're transporting: that's explictly defined to be payloads in the 64-255 range. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-04-03 01:42:56 +02:00
onionmsg
BOLT 12: offers, sixth draft A BOLT11 "invoice" has proven too low-level for human use in many scenarios. Efforts like lnurl have covered the gap, but integrating some of such higher layers into the lightning protocol itself has many advantages. This draft defines three new things: 1. A new invoice format. I know, this is painful, but it maps almost 1:1 to the current format (though signatures are very different), is easier to implement, and easier to send via the lightning network itself. 2. Formats for an "offer", which for all intents and purposes serves as the new, persistent invoice for users. 3. Format for an "invoice_request": this is a message sent via the lightning network itself to receive the real invoice, or can be used directly in a send-money scenario (e.g. ATM). The offer (for accepting payments) or invoice_request (for sending payments) are usually presented via a QR code or similar, the replies are sent using onion messages. Each copies fields from the prior so it stands alone, to allow statelessness. Features which have been deliberately omitted for the initial version: - Recurrence. - Invoice replacement ("don't accept that old payment!") - Payer proof for refunds. This effort has been EPIC, and there is absolutely no way I could have done this without the often thankless task of implementing, re-implementing, revising and re-reading this text. In particular I have been delighted to receive the mental boost from the following people: 1. Thomas H of ACINQ (https://github.com/thomash-acinq) 2. Jeffrey Czyz of Square Crypto (https://github.com/jkczyz) 3. Joost Jager (https://github.com/joostjager) 4. Aditya Sharma (https://github.com/adi2011) 5. Rene Pickhardt (https://github.com/renepickhardt) 6. Bastien Teinturier of ACINQ (https://github.com/t-bast) 7. Valentine Wallace of LDK (https://github.com/valentinewallace) 8. Matt Corallo of LDK (https://github.com/BlueMatt) Also @bjarnemagnussen, @ellemouton, @animatedbarber, @617a7a, @instagibbs, @evansmj, @eupn and @yyforyongyu. (And no doubt others over the years, who I've accidentally omitted!) Yes, of course, thanks to my family for their patience with me. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2024-09-24 10:31:04 +02:00
unrequested
Merkle
whitespace
TLVs
LnLeaf
LnNonce
LnBranch
payinfo
Fix typo and aspell list. (#963) Since Travis died, we don't get CI to check these any more :( Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-02-25 12:17:18 +01:00
griefing
unspendable
pkh
kB
Bolt 4: add blinded payments Add specification requirements for using route blinding to make payments while preserving recipient anonymity. Implementers must ensure they understand all those requirements, there are subtle attacks that could let malicious senders deanonymize the route if incompletely implemented.
2022-04-11 18:37:01 +02:00
unblind
BOLT 4: onion message support. These use onion encoding for simple one-way messaging: there are no error returns. However, every onion uses route blinding *even if it doesn't need to*. You can prove what path was used to reach you by including `path_id` in the encrypted_data_tlv. Note that this doesn't actually define the payload we're transporting: that's explictly defined to be payloads in the 64-255 range. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-04-03 01:42:56 +02:00
unblinded
interactive-tx: Add dual-funding flow, using the interactive tx protocol This commit adds the interactive transaction construction protcol, as well as the first practical example of using it, v2 of channel establishment. Note that for v2 we also update the channel_id, which now uses the hash of the revocation_basepoints. We move away from using the funding transaction id, as the introduction of RBF* makes it such that a single channel may have many funding transaction id's over the course of its lifetime. *Later, also splicing
2021-03-03 04:10:33 +01:00
workflow
PUSHDATA
prev
vout
rbf
standardness
perkw
prevtx
ints
replaceability
disincentivize
Add section about liquidity griefing This issue is non-trivial and worth mentioning, otherwise implementations may forget to handle this which would result in an easy way of attacking node's on-chain liquidity, creating a large opportunity cost.
2023-02-10 10:59:02 +01:00
UTXOs
Reference in New Issue Copy Permalink