Added ability to configure LXMF destination stamp value

This commit is contained in:
Mark Qvist 2026-11-17 16:33:23 +01:00
parent c47f9e4d97
commit 415559f731
No known key found for this signature in database
2 changed files with 25 additions and 1 deletions

View file

@ -1018,6 +1018,12 @@ The number of minutes between each automatic sync. The default is equal to 6 hou
On low-bandwidth networks, it can be useful to limit the amount of messages downloaded in each sync. The default is 8. Set to 0 to download all available messages every time a sync occurs.
<
>>>
`!stamp_value = 25.0`!
>>>>
The target stamp value for your LXMF destination can be configured with this option. Defaults to 25.0. Each increase of 1.0 doubles the generation difficulty. Destination stamps are one-time generations, so it can be worth targeting a high value here, to ensure that other transport nodes will accept your announces. The default should be sufficient for most cases, though.
<
>>>
`!required_stamp_cost = None`!
>>>>
@ -1215,6 +1221,18 @@ Determines whether the node server should be started on launch. Must be a boolea
Defines what the announced name of the node should be.
<
>>>
`!stamp_value = 25.0`!
>>>>
The target stamp value for your node destination can be configured with this option. Defaults to 25.0. Each increase of 1.0 doubles the generation difficulty. Destination stamps are one-time generations, so it can be worth targeting a high value here, to ensure that other transport nodes will accept your announces. The default should be sufficient for most cases, though.
<
>>>
`!link_cost = 17.8`!
>>>>
The link stamp cost required for other peers to connect to your node. The default is a relatively high value, that should deter most automated scraping and misuse, but you can set it even higher, if you wish, or lower it to allow connecting more easily.
<
>>>
`!announce_at_start = yes`!
>>>>