New Discord Announcement from THORChain Devs #🚨thornode-mainnet

### Solana Launch Preparation

Solana has been live on `stagenet` for 6 weeks without issue. The team plans to proceed with `mainnet` enabling on February 4 around midday US time. If there are no operational issues or fixes that take priority, the plan will be as follows:

1. Nodes should prepare a Solana RPC, whether self hosted (nothing is provided in `node-launcher` due to hardware requirements) or with a provider of choice.
2. Churning will be halted on Sunday February 1 to ensure the churn adding Solana to vaults occurs midweek.
3. Nodes will be instructed to enable Solana scanners approximately 24h before the intended churn on February 4.

Since the majority of nodes will find it cost prohibitive to run their own Solana nodes, the network will be leveraging external providers for the chain. In order to prevent a single provider from being able to eclipse attack or cause outage, nodes should distribute across a variety of providers. Please `make mimir` and set `SOL-RPC-PROVIDER` to one of the following values, indicating which provider you plan to use. If your provider already has a 20% share of nodes, please choose a different provider. If you are using a provider not in this list, please `make relay` it and we will add a corresponding voting key.

```
1 => Self Hosted
2 => Liquify (reach out to Andy or Isaac)
3 => QuickNode
4 => Alchemy
5 => Chainstack
6 => Ankr
7 => Blockdaemon
8 => Helius
```

It is a prerequisite for launch that 80% of nodes have designated an RPC provider via the mimir vote, and no single provider is above 20% dominance. If that condition is unmet by February 1, the timeline will be delayed.

@everyone

⚡️LIVE NOW ON X - Saturday Community Hangout w/ LetsExchange

Click here to join our weekly discussion on THORChain's latest developments.

https://x.com/THORChain/status/2014804468554944801?s=20

🚨 Live Now For Our First Video Livestream with Chad Barraford

All of the latest updates and THORChain alpha and why 2026 is the year of DeFi and THORChain to rule DeFi once and for all.

Click here to join:

https://riverside.com/studio/thorchain-8k6Ow?t=18027ffd26b586b991d6

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.15.1 (Bifrost Only)
https://gitlab.com/thorchain/thornode/-/releases/v3.15.1

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: ASAP

This is a Bifrost-only patch release containing a fix for a bug preventing observations of outbounds in the same block of a cancelled stuck transaction. Please `make pull` and `make install` to apply.

There are also a number of dropped mempool outbounds that require a quorum of the culprit vault to perform manual steps to clear the outbounds and complete churn. This has been historically infrequent, but has occurred a few times in the past months - the team is still discussing the safest path to handle this automatically in a future release.

```
node_address
vault status operator
kgy6 Active 5fjr thor...jz7t
5n2m thor...2rpj
9v7p thor...l8rt
dpwz thor...star
fywf thor...dvsr
j7dg thor...quu3
m62d thor...mlrc
m62d thor...ysvy
pgtt thor...j53w
s7en thor...kvg4
smfq thor...63d0
tf9u thor...z5cj
yqu0 thor...0653
zarc thor...nvm8
zarc thor...9yap
zga0 thor...5qsh
Standby k6jt thor...496v
```

If you are a node in the set above, please perform the following:
```
make debug
# select cosmosfullnode
# select thornode
# select bifrost
rm -rf /var/data/bifrost/observer/BTC/
# exit shell and ensure bifrost starts back up
```

@everyone

⚡️ We Are Live On X, LinkedIn, and YouTube

Join our video livestream right here as we dive into everything the BiorLabs App is bringing to crypto newbies and veterans

https://riverside.com/studio/thorchain-8k6Ow?t=18027ffd26b586b991d6

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.15.2 (Bifrost Only)
https://gitlab.com/thorchain/thornode/-/releases/v3.15.2

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: ASAP

This is a Bifrost-only patch release containing a few fixes for races in the TRON client signing that are causing stuck outbounds. Please `make pull` and `make install` to apply. We are hopeful these fixes will clear the TRON outbound queue once adopted by a quorum of all vaults. Once all stuck outbounds have cleared, it should be safe to resume TRON trading.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## GAIA 26.0.0❗️VALIDATORS ONLY

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: 12h

This install includes a required upgrade for Gaia `26.0.0` scheduled tomorrow at https://www.mintscan.io/cosmos/block/29837600.

```
make pull
make install
```

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.15.3 (Bifrost Only)❗️ENABLE SOLANA
https://gitlab.com/thorchain/thornode/-/releases/v3.15.3

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: 24h

This is a Bifrost-only patch release containing a final Solana fix and enabling the scanner by default. Please `make pull`, set the Bifrost environment variable `BIFROST_CHAINS_SOL_RPC_HOST` to your RPC provider, then `make install` to apply.

We will wait 24 hours from the time of this message. Then once a quorum of all vaults are scanning Solana at tip, we will unhalt churning and proceed to keygen Solana vaults.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.16.0
https://gitlab.com/thorchain/thornode/-/releases/v3.16.0

NETWORK: MAINNET
TYPE: Non-coordinated
URGENCY: 24h

The upgrade proposal has passed. Please install to schedule the upgrade at the proposed height. Nodes will automatically update to the new image at the scheduled height, and the node version for active validators will be automatically set at that time. All non-active validators must run `make set-version` after the upgrade height to be eligible for the subsequent churn. Solana will be safe to resume after the upgrade.

```
make pull
make install
```

Please note that this build contains private security patches, but they are not consensus breaking so the tagged release on Gitlab is valid for consensus.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.16.1❗️VALIDATORS ONLY
https://gitlab.com/thorchain/thornode/-/releases/v3.16.1

NETWORK: MAINNET
TYPE: Non-coordinated
URGENCY: ASAP

This is a Bifrost patch release containing a fix for EVM chain scanners preventing aggregator swap-ins.

```
make update
```

Then verify your node version is properly set to `3.16.1` and `make set-version` if the automatic version set did not apply. Once a quorum of the network has updated it is safe to resume EVM chain trading.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

**Vote ADR-23: Reserve Restructuring**

[ADR-23 Proposal Full Text](https://gitlab.com/boonew/thornode/-/blob/develop/docs/architecture/adr-023-rune-supply-restructure.md)

Summary of proposal:
1) Burn ~87% of the Reserve (~65m RUNE): https://runescan.io/address/thor1dheycdevq39qlkxs2a6wuuzyn4aqxhve4qxtxt
2) Reduce the Maximum Supply to 360M to protect the FDV supply reduction

Other Considerations:
- This change is a change in tokenomics, which usually requires broad community consensus and further outreach (eg Binance)

ADR Discord channel:
<#1473355028503728311>
ADR-23 Discussion Thread: https://discord.com/channels/838986635756044328/1473355821533368432/1473355899186970748

To vote on this ADR, nodes should:
`make mimir`
key: `ADR23`
values:
`1` to vote for
`0` to vote against
Check current vote status [here](https://rune.tools/voting?key=adr23)

Please `make relay` with explicit dissenting opinions, or contribute to the discussion thread (link above). This ADR will pass once >2/3 of the active validator set approves.

Thanks for participating @here

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

**Nine Realms Transition Announcement**

After several years contributing to THORChain's development and operations, over the next six weeks, Nine Realms will be gradually stepping back from our active roles in the ecosystem. There is a thread on this topic, please follow here for more info/discussion.

https://discord.com/channels/838986635756044328/838986636665815072/1483511027478958150

New Discord Announcement from THORChain Devs #🛡interface-alerts

## Router V6

The new router version alleviates issues with out-of-gas outbounds to smart contract wallets, and paves the path for future work to batch outbounds and support direct token transfers to vaults. The new router is live on all chains in `stagenet` and all integrators that are able are requested to test their flows there and flag any concerns.

We plan to upgrade the routers at the first churn of the week Tuesday or later, every 2 weeks, in order of increasing TVL:
- BASE (~$100k): week of March 30
- AVAX (~$500k): week of April 13
- BSC (~$1m): week of April 27
- ETH (~$12m): week of May 11

The router upgrade runbook for a given chain is as follows:
1. Set `MimirUpgradeContract<chain>=1`
2. Set `Halt<chain>Trading=1` 1h in advance of churn
3. Set `StopSolvencyCheck<chain>=1` 10 minutes before churn
4. Wait for churn to complete
5. Set `EVMAllowanceCheck-<chain>=1` to unblock token outbounds
6. Set `StopSolvencyCheck<chain>=0` to re-enable solvency check
7. Wait 1h to ensure no observed issues
8. Set `Halt<chain>Trading=0`

### ‼️Loss of Funds‼️
All integrators must ensure they are using the vault and router from `/thorchain/inbound_addresses` or the `/thorchain/quote` endpoints. Do not hardcode the router or cache the router and vault address independently. Every vault maps to exactly one router, and if sent to the wrong router for a vault funds will be lost. If funds are sent to a new vault with the old router, funds are lost. If funds are sent to an old vault with the new router, the inactive vault refund will fail and funds are lost.

Please reach out to devs in thread with any questions.

@here

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

### Nine Realms Endpoints
There are still a significant number of clients leveraging 9R public endpoints. We will be placing temporary redirects in front of our endpoints starting tomorrow to point at alternate locations on Liquify and others. The redirects will help to smooth the transition, but they will only be in place for a few weeks and clients may not automatically handle redirects.

All clients are recommended to migrate ASAP to avoid disruption. More details in announcement: https://discord.com/channels/838986635756044328/1161364032306028635/1483521870346191003

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE 3.16.3❗️GAIA 27.1.0❗️VALIDATORS ONLY
https://gitlab.com/thorchain/thornode/-/releases/v3.16.3

NETWORK: MAINNET
TYPE: Non-coordinated
URGENCY: ASAP

This is primarily a Bifrost patch release containing a minor fix to reduce likelihood of the first token outbound for a vault on router V6 being delayed by one reschedule. We will keep `BASE` trading paused until a quorum of all vaults has adopted to prevent poor UX. The patch release also exposes supply endpoints for CMC and similar, so those services may be migrated from the custom 9R endpoints to any `thornode` API provider.

Included in this install is a critical scheduled update for Gaia `27.1.0` occurring in ~20h. Please also note that there were some lint changes that went into `node-launcher` recently, which will result in whitespace and format diffs on most charts during apply.

```
make update
```

Then verify your node version is properly set to `3.16.3` and `make set-version` if the automatic version set did not apply.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE 3.16.4❗️MAINNET❗️VALIDATORS ONLY
https://gitlab.com/thorchain/thornode/-/releases/v3.16.4

NETWORK: MAINNET
TYPE: Non-coordinated
URGENCY: ASAP

This is a Bifrost patch release containing a fix to prevent Solana double spend (one occurred yesterday when 1/3 of nodes fell behind on observations). Once a quorum of all vaults have adopted, it will be safe to resume Solana trading and signing.

```
make update
```

Then verify your node version is properly set to `3.16.4` and `make set-version` if the automatic version set did not apply.

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

**ADR-25: Update Dev Fund Address <a:votingparrot:857384577382482010> **

With Nine Realms stepping back from the project, we need to send the dev fund to a new address. Discussion has been open for a week with no one voicing any concerns around this change. This is largely a housekeeping change rather than something controversial.

I want to make sure this change is in the next release (3.17) which should be cut on April 5th. There is a [tiny MR](https://gitlab.com/thorchain/thornode/-/merge_requests/4698) to make this change which is approved by devs but not merged yet. We'll give nodes the next few days to vote on this ADR or use `make relay` to make arguments against this change, but I expect there to be no resistance here, imo.

Full writeup of ADR 25 is [here](https://gitlab.com/thorchain/thornode/-/blob/develop/docs/architecture/adr-025-migrate-dev-fund-address.md?ref_type=heads), if anyone wants to read it.

ADR Discord channel: <#1488477141019529357>

To vote on this ADR, nodes should:
make mimir
key: ADR25
values:
`1` to vote for
`0` to vote against

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## GAIA 27.2.0❗️VALIDATORS ONLY

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: 24h

This install includes a required upgrade for Gaia `27.2.0` scheduled tomorrow at https://www.mintscan.io/cosmos/block/30675400.

```
make pull
make install
```

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

### Stuck Churn

There is stuck Solana outbound that was successfully broadcast, but later dropped from mempool and now blocking churn completion. There will be a patch in a future version to handle this circumstance. Nodes in the culprit vault `thorpub1addwnpepqdrf73rpn0ew26ds2v544dtdg782m3a0uvhaxdaxzdjd7k2ylt932n3pqvu` are requested to clear their Solana signer cache to allow the outbound to be re-attempted.

```
thor1yak0z56elhcfqw7xn7wjmp43ndnnxgfcmwkwex
thor1vvmt4q6h7w4gckcjh22z6ltjcppjz3laydnfzq
thor1ug5gy49ges0umfna70gpccj3rae4n0px2qmv82
thor100m5hh9qayap0edmvl9h8er4z6uesnfazjmefg
thor1krwlgcs3q7duapyxwxzpra5779fgh5gzh6gfaq
thor1agftrgu74z84hef6dt6ykhe7cmjf3f8dcpkfun
thor1kj56aupxnkhhy0rpdcp2gjncm4y78nnhjv496v
thor1h4kjq4xrxsm7ajpkstqgp9jcwxlc8khyfpwkfr
thor18h4xkczkd7g765n647t8clzp58cqet44n9s69g
thor1raynyffujzs7wqujwtnyp9ryludjvpe0s9tacs
thor1hjpct8pd9d48vyqltaqunltwx9twm57l3qmaya
thor19uyg2vvsja9cfpejdj0c6pm7exfk87envj5s5h
thor15qcqwmwu002gfu4ynwee5nhqy62j268e3dmw0q
thor1va3av7xeq57jyy5jr3wumw3ezg6vs6ldy9geqf
thor12espg8k5fxqmclx9vyte7cducmmvrtxll40q7z
thor1d7rerzkzus2t6v2yv9wuw9xg8a8aqse8p6nvm8
thor1sh72x9rac8ahkya76zljql3mw7t96ywsjlzw0n
thor15x0q6r84n2ac38gdlrct5ncchj5d4cr76jfaaf
thor1fuw5nemuww2gclznelfrdzpj6eml0fnmhgphew
```

If you are a node in the set above, please perform the following:
```
make debug
# select cosmosfullnode
# select thornode
# select bifrost
rm -rf /var/data/bifrost/observer/SOL/
# exit shell and ensure bifrost starts back up
```

Once a quorum of the vault have cleared their signer cache and the outbound can be sent and churn can complete.

@here

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

THORNODE ❗️MAINNET❗️UPDATE 3.17.0
https://gitlab.com/thorchain/thornode/-/releases/v3.17.0

NETWORK: MAINNET
TYPE: Non-coordinated
URGENCY: 20h

The upgrade proposal has passed. Please install to schedule the upgrade at the proposed height. Nodes will automatically update to the new image at the scheduled height, and the node version for active validators will be automatically set at that time. All non-active validators must run make set-version after the upgrade height to be eligible for the subsequent churn.

```make pull
make install```


@everyone