Skip to content

Commit 7e143ea

Browse files
skunk-inkn8maninger
authored andcommitted
Updated language in v2/exchanges.md for post June 6th
1 parent 6618d4b commit 7e143ea

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

v2/exchanges.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ layout:
1717
This guide is for exchanges that are currently using `siad` to track and manage Siacoin deposits. Exchanges should upgrade to `walletd` before the V2 hardfork to continue supporting the Sia network.
1818

1919
{% hint style="info" %}
20-
The hardfork activates at a block height of **526,000** on or around **June 6th, 2025 06:00 UTC**.
20+
The hardfork activated at the block height of **526,000** on or around **June 6th, 2025 06:00 UTC**.
2121
{% endhint %}
2222

2323
`walletd` is the new reference wallet for exchanges. It is designed to be more secure, reliable, and scalable than `siad`. `walletd` also has a more robust API, supports multiple wallets simultaneously, and provides easier support for secure key management setups.
@@ -642,7 +642,7 @@ func main() {
642642

643643
## How to Support V2?
644644

645-
After block height **526,000** (estimated **June 6th, 2025 06:00 UTC**), `siad` will no longer be able to send or receive Siacoins. To continue supporting the Sia network, exchanges must upgrade to `walletd`. In addition to upgrading to `walletd`, exchanges will need to start sending V2 transactions and using the new V2 API endpoints.
645+
After the block height **526,000** (estimated **June 6th, 2025 06:00 UTC**), `siad` is no longer be able to send or receive Siacoins. To continue supporting the Sia network, exchanges must upgrade to `walletd`. In addition to upgrading to `walletd`, exchanges will need to start sending V2 transactions and using the new V2 API endpoints.
646646

647647
### Sending V2 transactions
648648

0 commit comments

Comments
 (0)