oars
f5a3eb84c0
bin/lilith: don't exit loop when whitelist_host and greylist_host methods return error
2026-02-03 20:49:59 +02:00
x
436e5fe13e
net: Simplify Hosts to use a single lock
2026-01-20 09:31:52 +00:00
skoupidi
fcf4aded0e
darkfid: split managemtn rpc methods into its own rpc server and standarized all ports
2026-01-02 19:41:34 +02:00
x
fcdf5ee488
chore: Update crate dependencies
2026-01-01 19:48:04 +00:00
x
9785777642
chore: Update copyright license year
...
Happy 2026!
2026-01-01 11:40:45 +00:00
oars
9cc3046f23
bin/lilith: DEP-0007: rename allowed_transports, manually add default network profiles for all schemes public nodes possibly can use
2025-12-30 11:30:54 +03:00
oars
9e119068fa
bin/lilith: DEP-0006: manually add app identifier for each p2p network in lilith config
2025-12-30 11:30:54 +03:00
oars
fcf0571a1a
bin: set unique magic bytes for each seprate p2p network
...
- add magic bytes to p2p net configs for bins
- hardcode darkirc and fud magic bytes in bin/app darkirc and fud plugins
- make lilith use the separate magic bytes for different p2p networks
2025-12-30 11:30:54 +03:00
x
add9bb596c
chore: Update crate dependencies
2025-12-25 12:22:56 +00:00
x
aa537b9e4b
chore: Update crate dependencies
2025-11-24 12:12:14 +02:00
oars
d85cf80dbf
replace log imports with tracing everywhere
2025-11-07 10:15:36 +03:00
oars
ac0365cc60
Cargo.toml, Cargo.lock: change dependencies used for logging
...
- replace log crate with tracing,
- replace simple-log crate with tracing-subscriber and tracing-appender
- add nu-ansi-term crate as a dependency which is itself tracing-subscriber's dependency,
inorder to write colored outputs to the terminal since we override formatting provided
by tracing-subscriber
2025-11-07 10:15:36 +03:00
parazyd
fda2a84034
chore: Update dependencies
2025-08-05 09:41:05 +02:00
oars
c183c6f377
net,bin/lilith: allow localhost to be blacklisted in localnet mode, this will allow us to test banning/blacklisting features
2025-07-07 17:53:09 +03:00
skoupidi
d40fc89a2d
lilith: chore clippy
2025-06-28 17:15:40 +03:00
parazyd
46d815ace0
chore: Update crate deps and freeze RandomX git rev
2025-05-21 15:01:54 +02:00
parazyd
e002530bb2
chore: Update packages to v0.5.0
2025-05-09 11:32:44 +02:00
parazyd
aa6d65f472
lilith: Update config
2025-05-07 17:06:53 +02:00
parazyd
81f37b7b2a
chore: Update crate dependencies
2025-05-03 10:35:40 +02:00
oars
c73e8607bc
net: add i2p transport
2025-04-23 13:21:09 +03:00
parazyd
c040d9c00f
chore: Update crate dependencies
2025-04-15 10:49:43 +02:00
Paul Otten
721502a468
Move from "nightly" toolchain to "stable".
...
Intended to address tau RefID "Gifn1u".
There are still a few things that require nightly.
- cargo +nightly fmt
- fuzzing
2025-04-14 19:42:15 -04:00
parazyd
f5baac83cf
chore: Update crate dependencies
2025-02-25 12:15:28 +01:00
skoupidi
a671d43cee
chore: fmt and fixed minor comments inconsistencies
2025-02-19 13:54:38 +02:00
darkfi
2bbe39e0ee
use RpcSettings and RpcSettingsOpt
2025-02-19 13:21:12 +02:00
parazyd
13620224c0
chore: Update crate dependencies
2025-02-09 10:32:33 +01:00
parazyd
604f443fd1
chore: Update license header year
2025-01-24 10:36:02 +01:00
parazyd
b5d7c52191
chore: Update crate dependencies
2025-01-21 14:21:32 +01:00
skoupidi
a76b9526bc
misc: use ~/.local/share/darkfi for app storage
2025-01-13 15:25:15 +02:00
skoupidi
bc22307e8b
rcp/server: generalize RequestHandler so we can create multiple instances of it
2024-12-05 16:22:43 +02:00
parazyd
fbe6937a20
chore: Update crate dependencies
2024-10-15 16:08:54 +02:00
parazyd
242fe81658
chore: Update crate dependencies
2024-10-01 14:15:03 +02:00
skoupidi
82520041eb
chore: clippy elided lifetimes
2024-09-17 16:56:38 +03:00
dasman
0cb128ebb9
net: fix args conflicting by replacing p2p datastore arg to p2p_datastore
2024-09-08 11:03:05 +03:00
parazyd
165cb8434b
chore: Update crate dependencies
2024-08-29 20:39:22 +02:00
skoupidi
67604acf47
chore: removed duplicate features imports
2024-08-29 18:47:21 +03:00
draoi
68b63a76e9
dnet+lilith: rename anchorlist to goldlist
2024-07-17 15:52:39 +02:00
draoi
9dd240f13e
net+lilith: introduce BanPolicy
...
We create a new net Setting called BanPolicy that can be Strict or
Relaxed. If it's set to Strict, we ban peers that send messages without
us having a corresponding Dispatcher. If it's set to Relaxed we simply
close the connection.
Lilith is set to Relaxed by default while other peers are set to Strict.
This helps us avoid Lilith blacklisting peers that send messages for
protocols it is not subscribed to.
2024-07-17 14:36:28 +02:00
parazyd
27fd3785f8
chore: Update crate dependencies and CI Rust version
2024-07-09 12:20:06 +02:00
parazyd
7945e2eb18
net: Implement mutable Settings which allow dynamic reconfiguration
2024-07-09 11:22:55 +02:00
draoi
df8c1a8e86
lilith: fix logic error that was causing responsive nodes to be sent to greylist
2024-07-06 20:41:29 +02:00
draoi
3acf49e6a0
net: use standardized methods for net and lilith refinery's
2024-07-06 20:41:29 +02:00
parazyd
c6227e38e4
net: Create datastore in P2p::new()
2024-07-05 11:17:58 +02:00
parazyd
ee147076b3
lilith: Fix typos in config file
2024-07-05 10:55:38 +02:00
parazyd
c6aa5c1544
net: Define a datastore path
2024-07-02 11:51:42 +02:00
parazyd
ba62cdf6e5
net/settings: Convert hostlist into an Option<String>
2024-07-02 11:45:06 +02:00
draoi
2cd8b4dff7
net: use sync Mutex for HostContainer
...
Rationale: using a sync Mutex wherever possible is the recommended
method.
Additionally, using a sync Mutex here fixes some really weird fairness
behaviors we observed in the smol::lock::RwLock where writers in the
priority queue were occassionally ignored.
2024-06-27 15:03:22 +02:00
draoi
958361c953
net: simplfy fetch_last() method and fix lilith's usage
2024-06-26 10:24:06 +02:00
draoi
6a0d4cfe7d
net: simplify update_last_seen() method
...
Also fix its usage by Lilith
2024-06-26 10:01:42 +02:00
draoi
dbf5c6bc8f
hosts: use sync Mutex for HostRegistry
...
We don't need to use an AsyncMutex here since we're not holding across .await points or for long periods of time.
Using a sync Mutex here also fixes some really weird fairness behaviors we observed in the smol::lock::Mutex where writers in the priority queue were occasionally getting ignored. This was apparently not a deadlock since subsequent and prior readers and writers were able to access the data with no problems.
2024-06-26 08:52:46 +02:00
