Skip to content

Commit 3ef6979

Browse files
authored
Merge pull request #3005 from XRPLF/blog-xrplf-unl-update
Blog post - move to new foundation commences
2 parents 1da5893 + 973665f commit 3ef6979

File tree

2 files changed

+98
-0
lines changed

2 files changed

+98
-0
lines changed
Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
category: 2025
3+
date: 2025-02-19
4+
seo:
5+
title: Move to the New Foundation Commences
6+
description: With the new XRPL Foundation now incorporated in France, the Founding Members are migrating assets from the previous entity. Learn about the Unique Node List (UNL) transition and necessary actions for community members.
7+
8+
labels:
9+
- General
10+
markdown:
11+
editPage:
12+
hide: true
13+
---
14+
# Move to the New XRPL Foundation Commences
15+
16+
_By the XRPL Foundation_
17+
18+
Late last year the initial groundwork for the launch of the new XRPL Foundation was laid, including the [incorporation of the new Foundation](../2024/a-new-era-for-the-xrp-ledger.md) in France. This major milestone has enabled the Founding Members (XRPL Commons, XRPL Labs, Ripple, and XAO DAO) to continue with immediate next steps. In line with this, the migration of assets (listed in an [earlier blog post](../2024/a-new-era-for-the-xrp-ledger.md)) from the previous entity to the newly established Foundation is now underway.
19+
20+
The migration includes the transition of the Unique Node List (UNL) published by the old XRPL Foundation to the new XRPL Foundation. Importantly, any validators and node operators that rely on the old UNL will need to update their configurations to reflect the new Foundation’s infrastructure.
21+
22+
To ensure continued network participation and avoid potential downtime, validators and node operators must take this action **by Monday, March 10, 2025**.
23+
24+
### Why this Transition Matters
25+
26+
Throughout its history, the XRPL Foundation has played a critical role in maintaining the security and decentralized status of the XRPL by publishing a trusted UNL. Validators and node operators are able to contribute to maintaining an up-to-date, secure, and well-managed network by updating their configurations to the new UNL, ensuring a smoother and more reliable blockchain infrastructure.
27+
28+
### Required Actions for Validators
29+
30+
Ahead of the migration date, validators need to take the following actions:
31+
32+
1. Update their configuration to reflect the new cryptographic public key provided by the new Foundation.
33+
2. Restart their node to apply the updated configuration.
34+
35+
Failure to complete these actions may result in network disruptions, impacting connectivity and participation in consensus processes.
36+
37+
Detailed instructions of the actions validators and node operators are required to take are below.
38+
39+
The transition to the new XRPL Foundation marks an important step in ensuring the continued stability and security of the XRPL network. Validators and node operators play a pivotal role in this process, and their timely action is crucial for maintaining a robust and decentralized infrastructure.
40+
41+
As the migration from the old to the new Foundation progresses, additional support and updates will be provided on XRPL.org to ensure a seamless transition for all participants.
42+
43+
44+
## Actions To Take
45+
46+
### Steps
47+
48+
If your XRP Ledger node currently trusts the UNL published by the XRP Ledger Foundation, complete the following steps to update your settings:
49+
50+
1. **Edit `validators.txt`**
51+
52+
Update the `[validator_list_keys]` section (the current endpoint remains unchanged) to replace the old key (`ED45D1840EE724BE327ABE9146503D5848EFD5F38B6D5FEDE71E80ACCE5E6E738B`) with the following:
53+
54+
```
55+
[validator_list_keys]
56+
ED42AEC58B701EEBB77356FFFEC26F83C1F0407263530F068C7C73D392C7E06FD1
57+
```
58+
59+
2. **Restart `rippled`.**
60+
61+
After saving the changes, restart your `rippled` service. On supported platforms, you can run the following command:
62+
63+
```sh
64+
sudo systemctl restart rippled.service
65+
```
66+
67+
3. **Confirm the new settings**
68+
69+
Run:
70+
71+
```
72+
/opt/ripple/bin/rippled validators
73+
```
74+
75+
The output should display the updated values in the `publisher_lists` key:
76+
77+
```json
78+
{
79+
"result": {
80+
"local_static_keys": [],
81+
"publisher_lists": [
82+
{
83+
"available": true,
84+
...
85+
"list": [
86+
...
87+
],
88+
"pubkey_publisher": "ED42AEC58B701EEBB77356FFFEC26F83C1F0407263530F068C7C73D392C7E06FD1",
89+
"seq": 1,
90+
"uri": "https://vl.xrplf.org",
91+
"version": 1
92+
},
93+
...
94+
]
95+
...
96+
}
97+
```

blog/sidebars.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66
- group: '2025'
77
expanded: false
88
items:
9+
- page: 2025/move-to-the-new-xrpl-foundation-commences.md
910
- page: 2025/rippled-2.3.1.md
1011
- page: 2025/devnet-reset.md
1112
- page: 2025/vulnerabilitydisclosurereport-bug-nov2024.md

0 commit comments

Comments
 (0)