-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add restriction per
for lightningd runes
#6617
Add restriction per
for lightningd runes
#6617
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments, and importantly, still needs test for per...
b22e50b
to
1ab4d91
Compare
1ab4d91
to
0ad399c
Compare
0ad399c
to
7a2008f
Compare
7a2008f
to
f7143a0
Compare
Ack f7143a0 |
Ah, you can't call your helper function |
We will use this for better rate limiting
f7143a0
to
6d400a4
Compare
Changelog-Added: JSON-RPC: `showrunes` new field `last_used`
json_add_timeabs only printed in milliseconds and json_add_time outputs a string which is weird Changelog-Changed: JSON-RPC time fields now have full nanosecond precision (i.e. 9 decimals not 3): `listfowards` `received_time` `resolved_time` `listpays`/`listsendpays` `created_at`.
… restriction Changelog-Added: runes: `per=Nsec/min/hour/msec/usec/nsec` for general ratelimiting
6d400a4
to
968d5d9
Compare
Ah, and valgrind caught that we missed initializing a variable (if there's no rune in db, we left last_used uninitialized for json_add_rune). Fixed. This time for sure! |
No description provided.