Skip to main content

· 3 min read
Ale Banzas

Hello everyone from the weekly Gnosis Core Devs Call. This meeting is repeated on Wednesday every week. Watch on Gnosis Chain YouTube channel. ‍

Participants: Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis DevRels, Gnosis Comms team and the contributors.


At this week's short meeting, the latest status updates on the withdrawal contract was talked and possible implementation scenarios were evaluated. In addition, opinions were shared about Shanghai testing tools and POSDAO testnet. Updates from Core Dev Team updates on Erigon, Gateway, Nethermind, Geth, Prysm were included in the agenda.Additionally, updates from the Core Dev Team updates about Erigon, Gateway, Nethermind, Geth, Prysm were included in the agenda.


  • Withdrawals Contract
  • Core Dev Team updates
  • Shanghai testing tools
  • Base Fee

Let’s take a look at the core devs call updates.

Call Notes

Withdrawals Contract

  • Not many changes since last week
  • Waiting for feedback before continuing the implementation 3 possibilities 1. Declare that the GNO token on the GC is a canonical token Mint it when the contract has not enough tokens Violates the first principles of the GNO token 2. Mint an GNO on GC token when the contract has not enough tokens Violates the bridge pledge logic 3. Do not issue a token when the contract has not enough tokens, but instead leave a note that in the future the user will be able to receive funds if they will be on the withdrawal contract (violates the logic of creating an mGNO token because of staking) E.g. “promissory”GNO

Chain Infra

  • Gateway
    • 20% of Chiado traffic goes to Gateway RPC
    • Need to start getting traffic from Mainnet RPC

Core Dev Team updates

  • EL
    • Erigon
      • No updates
    • Nethermind
      • Working on running devnets for withdrawals with mock contracts
      • The withdrawal spec is going to be different on Gnosis than on mainnet, so testing would be quite useful
      • Wrote a script to verify if some bytecodes are used
      • Resource utilization is apparently lower than before
    • Geth
    • Philippe
      • Added Chiado chainspec to Lodestar
      • Added deposit blocks for Gnosis and Chiado to
    • Erigon
      • To allow for –prune=r without having to specify –prune.r.before=firstDepositBlock
      • WIP: Light clients for CL for Gnosis and Erigon
      • WIP: Nimbus + Erigon

Other issues

  • Bridge Coordinator
    • Will update in subsequent week


  • Gateway
    • Shanghai testing tools?
    • Igor might have been working on this already
    • Waiting for him and dapplion
  • POSDAO tests?
    • Need to add withdrawals tests

· 4 min read
Ale Banzas

Hello everyone from the weekly Gnosis Core Devs Call. This meeting is repeated on Wednesday every week. Watch on Gnosis Chain YouTube channel ‍

Participants: Erigon, Gateway, Nethermind, Geth, Gnosis Core Devs, Gnosis DevRels, Gnosis Comms team and the contributors.


During this week's meeting, the topic of the Withdrawal Contract was thoroughly discussed. The latest updates regarding xDai fees, which were brought to the table last week, were also discussed. Additionally, updates from the Core Dev Team (Erigon, Gateway, Nethermind, Geth, Prysm) were included in the agenda.


  • Withdrawals Contract
  • xDai “fees”
  • Core Dev Team updates
  • InterOp update
  • Base Fee

Let's take a look at the core devs call updates.

Call Notes

  • Chain Infra

  • Ale: from Discord

    • Source of “block rewards” GNO
      • Withdrawals contract (with Ihor)
      • Option 1: Large reserve that pays out GNO rewards (bridged from ETH)
      • Option 2: Hardfork to “mint” GNO on-chain native to Gnosis Chain
  • Withdrawals Contract

    • Current status
    • Need to decide on approach given differences between ETH & GNO
      • Ethereum = ETH is native, while mGNO is not
      • Withdrawals on GNO will “withdraw” it from the deposit contract
    • The “deposit contract” option is being taken for now Withdrawal contract will rely on “reserve” contract that will be funded before/after Treasury will need to send more GNO to the Withdrawal contrat to account for block rewards
    • Alternative approach
      • Minting mGNO on Gnosis Chain thru increment the mGNO token registry thru system call (i.e. “issue” mGNO)
      • Ihor: how do we maintain total token balance (i.e. sum(GNO on Ethereum chain) == 3_000_000)
    • There is no way to convert mGNO to GNO
      • Ihor is implementing mGNO to GNO unwrapping logic in the mGNO wrapper
      • Upgradeable contract
    • Long-term business direction
      • GNO on Ethereum is a “claim” against native GNO on Gnosis
      • Reduce dependency of GNO on GNO on Etheruem or Bridges
    • Need to write a forum post on Gnosis Forum
  • xDai “fees”

  • Core Dev Team updates

    • Erigon
      • Fixing issues with eth_blockNumber
      • Prep EIP-170 with Shanghai update
        • Contract code size limit
        • Previously omitted in Gnosis Chain - POSDAO had code size limit in POSDAO contract (permissionContract)
        • EIP-3860 - relies on EIP-170
      • Prep for Withdrawals work
    • Nethermind
      • Waiting on Withdrawals spec
      • Proof-of-concept implementation based on what Nethermind team knows about withdrawals
      • Can do some local testing on
      • Scanning chain for opcodes +
    • Gateway
      • Igor: This week we finalized Chiado checkpoint sync endpoint, I fixed some tracing issue in Erigon reported by our users, waiting for more traffic from Gnosis RPC
    • Geth
      • Full Sync
      • Snap Sync - some issues
    • Prysm
      • Merged the PR
      • Should be able to run stock on Prysm - pass in config file
      • Let Guillaume know if we encounter issues
  • Any other issues

    • Philippe: Erigon + Nimbus are publishing blocks
  • Base Fee

    • Spam protection
    • 1 gwei would allow it to kick in within ~10min of full blocks, vs hours
    • Tomasz had strong objections - should table it
  • InterOp update?

    • Withdrawals + Shanghai - shadowforks are working
    • SSZ in execution layer (vs RLP for txns)
      • SSZ (CL) vs RLP (EL)
      • Backward compatibility of txns in SSZ
    • EOF - shelved
    • Specs
      • Danube - 4844
      • Electra - verkle (Guillaume)
  • Consensus Spec tests

    • Needed for Nimbus merge

· 2 min read
Ale Banzas

Call Info

Hello everyone from the weekly Gnosis Core Devs Call. This meeting is repeated on Wednesday every week. Watch on Gnosis Chain YouTube channel ‍ Participants: Erigon, Gateway, Nethermind, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team and the contributors.


  • Shanghai upgrades details from Nethermind
  • RPC updates from Gateway
  • Suggestion from Stefan: Increase base fee to 1GWEI?

Let's take a look at the core devs call updates.


  • Chiado: Might be finished this month
  • Mainnet: Erigon got stuck while syncing mainnet twice, reboot helped
  • Also affects other networks
  • Not seen in 2.36.1 yet
  • Work going on for withdrawals (for Ethereum mainnet)
  • We should review the specs for Gnosis when everyone is back, because there’s some new context


  • Launched archival RPC (Gnosis mainnet)
  • Will launch a website with the new public RPC
  • Launching checkpoint sync for Chiado (probably today)
  • Fixed an issue with the rate limiter that was too eager
  • Looking into looking a bridge validator on Chiado, and then on mainnet
  • Waiting for Giacomo to accept traffic on the RPC


  • Implementation for withdrawals on Gnosis (and mainnet)
  • Only missing part is the smart contract used for withdrawals
  • Stefan: Ihor will write the contracts (WIP, ETA: 1 month)

Stefan: Increase base fee to 1GWEI? ‍

  • Allows us to make constant spamming very costly. Currently it is too cheap.
  • Current base fee: 7 wei -> extremely cheap to spam the network for a long time
  • Increasing the base fee to 1 gwei would make it expensive to spam the network even for 10 minutes
  • Would require a simple hard fork, which could be included in another hard fork ‍

Jorge (Nethermind)‍

  • No strong opinion
  • The computation limit is bound by the gas limit anyways
  • Sustained loads would increase the gas price exponentially as per EIP-1559
  • On Chiado, a spam of 30 - 60 minutes increased the base fee to hundreds of gwei
  • The main idea is to prevent nefarious actors to put relevant transactions on hold for some time, which would degrade user experience

Gnosis DevOps

  • Chiado RPC routing implemented (testing with Gateway), then mainnet
  • 2 Chiado long-term bootnodes
  • Update configs

· One min read
Lion - dapplion


At Block 6,306,357, the Gnosis Execution Layer network successfully merged with the Consensus Layer network.

The Merge was uneventful, which was the best possible outcome after months of hard work and testing by the team.

Resuming Bridge Operations

After a ~36 hour observation period, the Gnosis Governance Multisig proceeded to restore the pre-merge limits for the Bridge.

The xDai Bridge, Arbitrary Message Bridge and Omnibridge resumed regular operation at 10 Dec 2022 03:21 UTC.

· 2 min read
Lion - dapplion
deprecated update

Check the latest and recommended bootnodes in the network page.



  • On 7 Dec 2022, a subset of Bootnodes that were baked into the Gnosis client releases stopped functioning normally.
  • This resulted in instances of new nodes being unable to find peers unless they specified custom bootnodes.
  • This became a problem for newly-introduced nodes (current nodes unaffected).


  • Core Devs have put together a alternative list of temporary bootnodes that will be active for Dec 2022.
  • These Bootnodes are run by various teams in the Gnosis ecosystem.
  • Node operators will need to specify custom bootnodes when running a fresh Execution or Consensus node.
  • Core Devs will bake updated set of long-term Bootnodes into the next client releases

Execution Layer


Nethermind utilizes the flag --Discovery.Bootnodes to specify custom bootnodes.

Docs: Nethermind Github

--config xDai
--Discovery.Bootnodes ... # comma separated enode addresses

List of EL Bootnodes


Note: Temporary Nodes provided below are unlikely to be the long-term Bootnodes. You should not expect them to be operational post Jan 2022.

Comma-Separated Values




Consensus Layer


Teku utilizes the flag --p2p-discovery-bootnodes to specify custom bootnodes.


--p2p-discovery-bootnodes=... # comma-separated ENR addresses


Lighthouse utilizes the flag --boot-nodes to specify custom bootnodes.

Docs: Lighthouse CLI .help

--boot-nodes=... # comma-separated ENR addresses


Lodestar utilizes multiple --bootnodes flags to specify custom bootnodes.


--bootnodes=... # first ENR (1 per line)
--bootnodes=... # second ENR (1 per line)

List of CL Bootnodes


Note: Temporary Nodes provided below are unlikely to be the long-term Bootnodes. You should not expect them to be operational post Jan 2022.

Comma-separated Values


One-per Line


· 4 min read
Ale Banzas


  • Gnosis will be temporarily pausing its Native Bridges for the duration of the Merge
  • This is a risk-management operation that will be rolled back once normal operation of the chain has been verified post-Merge
  • This will affect both the Omnibridge and xDai Bridge, and any 3rd-party bridges or dApps that utilize the Native Bridge contracts.

Pausing of Bridges

24 hours prior to the Merge TTD (currently tracking for ~8th Dec 2022 18:43 UTC), the Gnosis Bridge Governance Multisig will execute a transaction to set the the following bridge parameters.

xDai BridgeDailyLimit set to 0 on all Bridge Contracts

This will prevent any transaction from going through.
Arbitrary Message Bridge
SetMaxGasPerTx set to 0 on all Bridge Contracts

This will prevent any arbitrary message call from going through.

Unpausing of Bridges

There will be an 96 hour observation period post-merge to ensure that the chain finalizes without incident. Once this observation period has passed without incident, the Gnosis Bridge Governance Multisig will execute the following transactions to restore the pre-Merge bridge limits. GnosisDAO may also elect to unpause the bridges earlier.

xDai BridgeLimits restored to Pre-Merge limits
Arbitrary Message Bridge
Arbitrary Messages can be sent.
Omnibridge limits restored to Pre-Merge limits


xDai Bridge

Bridge ContractInitial LimitTemporary Limit

AMB & Omnibridge

Ethereum - Gnosis

Bridge ContractInitial LimitTemporary Limit

Gnosis - BNBChain

Bridge ContractInitial LimitTemporary Limit
HomeGC <-> BSC
ForeignGC <-> BSC


Will the Bridge Contracts remain operational during this time?

  • Bridge Contracts are smart contracts, and remain active on chain
  • The "pause" refers to parameters that are being set on these smart contracts that effectively limit their usage

Will Bridge Validators continue to operate during this time?

  • Bridge Validators will continue to be operational, but will not relay any messages as the events they listen to will not trigger due to the limits set

Can my dApp continue to use the AMB?

  • The Arbitrary Message Bridge (AMB) will not relay messages between the supported networks, as _sendMessage requires a non-null gas limit.
  • Both the OmniBridge and xDai Bridge won’t initiate since the established values will prevent it.

Can I continue to use the Omnibridge?

  • No, you will not be able to use the Omnibridge as it depends on the Arbitrary Message Bridge, which is unable to relay messages due to the gas limit.

What are the conditions by which the bridges will be enabled again?

A few of the conditions we will be monitoring post-Merge:

  • Gnosis Chain should be able to finalize
  • Execution Layer and Consensus Layer "merge" without incident
  • Validators are not experiencing major issues
  • Bridge Validators are operational

After confirming the successful merge of Gnosis mainnet and the beacon chain, we will restore OmniBridge and xDai Bridge initial parameters.

· 13 min read
Archive Post

This post is more than one year old. The information may be outdated. Check the latest posts.

Representatives from xDai (Igor Barinov) and Gnosis (Stefan George) answered questions about the proposed merger. Questions were also collected throughout the past week and some are listed below. Questions below the AMA video give some additional context and see responses to popular questions that may not have been raised during the call.

The proposal is available here for reference.

Questions from the Community

We include some questions and answers here from the initial form sent out to the community. Some questions were redundant and not included, or edited for clarity. We will update with the recording and other relevant questions after the AMA.

1. What motivated the developers to propose this?

Both teams have worked together for some time, and looking ahead there are some big changes coming to Ethereum and associated scaling solutions. To come from a position of strength, it makes sense to combine forces and consolidate resources when two conditions are met:

  1. The teams share the same values in building technically excellent products in the spirit of open innovation. Both Gnosis and xDai are committed to fostering network effects without locking users in. Both Gnosis and xDai champion self-sovereign network participants.
  2. The technology stacks being developed by both teams compliment each other and together provide a comprehensive scaling solution for users.

2. Are the holdings of the developers in GNO and STAKE made public?

The initial STAKE distribution for the xDai team and investors is available here. These tokens have mostly been distributed and team holdings besides the distributions remaining to the ecosystem fund have been dispersed.

A partnership announced between the teams last year resulted a Gnosis investment in xDai for 250K STAKE.

Beyond these distributions STAKE tokens are held by the greater community and all trades are transparent on BlockScout & Etherscan. The following includes contracts holding STAKE as well as EOAs.

3. While Gnosis is planning to split the governance power of GNO into COW and SAFE for their other products, do you think it is reasonable to proceed with the merger based on the current value of GNO (which actually includes the governance value of their products that will likely have a separate governance token)? Why not wait for their token splits from GNO?

Gnosis holders will benefit significantly from the launch of the COW and SAFE tokens, both directly via an airdrop and a much coveted investment opportunity into the projects. The value of GNO is additionally backed by 700M in crypto assets (excluding GNO) that are in the process of being move to the DAO (and under the direct control of the GNO token holders)

  1. GNO holders will benefit directly from the token launches of the spin-off projects.
  2. GNO holders control a very significant treasury (USD 700M in ETH and other tokens, excluding GNO).

4. What changes will be made to the GNO issuance policy and distribution methodology?

400k GNO held by the DAO (currently ~190m USD) will be used to incentivize adoption of Gnosis Chain. The DAO (i.e. all current GNO holders) holds 8m GNO. It is likely that the DAO will decide to burn some of these tokens.

5. How can the merge benefit the xDai community with respect to the STAKE holders?

In the event of a merge, STAKE holders will become GNO holders and retain the ability to voice opinions and steer directions for the chain. STAKE holders will hold 20% of the GNO in circulation at the proposed token merge rate. The idea is that combining forces of these 2 projects will result in a stronger and more complete entity, with the hope that the market would acknowledge this and the Gnosis Chain & GNO would benefit accordingly.

6. How will the chain be secured? If only 1 Gno is req for running a node, the price of Gno needs to have a big upside or the chain can be easy overtaken by others? How will it be decentralized?

There will be many more validators with the beacon chain, along with random validator shuffling to prevent attacks and collusion. This is a good resource to understand how the validator and proposer functionality works and what to expect with the beacon chain (this is for the ETH Beacon chain but methods will work similarly on the mirrored beacon-chain The chain has the potential to be much more decentralized as many more regular users around the world can participate with a lower economic barrier to entry. There are some ideas to subsidize hardware to encourage participation.

7. What exactly are the metrics/statistics of some of the 'marketing objectives' / branding strength is Gnosis offering?

These types of metrics will be developed by a newly created team dedicated to marketing and project/application growth. There will be a strong commitment to growing and promoting the chain. Expect marketing initiatives with defined, transparent goals that have not been possible so far with xDai’s limited marketing resources.

8. How would the merge affect the existing projects like xDai Punks, xDai Tigers or even De-Fi Platforms like Agave and 1Hive ?

GnosisDAO will reserve 400k GNO (~$190 million) to develop the Gnosis Chain ecosystem and incentivize usage. GnosisDAO can consider adding liquidity to various DeFi protocols on the xDAI chain to support their adoption, including Agave and 1Hive. Aspiring NFT projects like xDai Punks, xDai Tigers and xDai Bots may consider rebranding to support the Gnosis brand (although xDai will still be the native transactional token, so no changes are required).

The base currency will remain as xDai, with all the benefits of a stable token. Transaction fees will still be paid with xDai. Governance and staking on the beacon chain will use GNO.

9. Seeing as xDai chain has the potential to offer the Ethereum ecosystem as a cheap and fast scalability solution, why is XDAI team going ahead with this merger proposal at a low conversion rate? All our price discovery potential is ahead of us, why is the team and Gnosis setting a 14-day TWAP price right before token price potentially goes exponential?

Unfortunately there is no crystal ball, so it's hard to say if the token price was headed in one direction or another. The community expectations for items like the London HF activation or rebranding initiatives (comparing the effort to the Matic -> Polygon rebrand) were likely not in alignment with the reality of the situation.

  • So far, less than 0.20 xDai has been burned with London activated for 3 days. This will increase if chain usage increases, however at this time the amount burned is insignificant and will not result in any tangible results from associated STAKE burn.
  • The branding refresh by RaidGuild is nearly finished with the purpose of clearing up confusion among the community and users. There was no planned name change etc. The primary goals include explaining dual token mode, purpose of the STAKE token in the ecosystem, creating new logos which are currently absent, etc.

10. If the xDai community isn't behind this trade will it be forced through by the team and Gnosis? Gnosis holds many hundreds of thousands of STAKE and we know which way they will vote, will they be ruled out of voting on this proposal so that we can see what the xdai community actually wants?

The GnosisDAO holds 250K STAKE, which makes them part of the community. Signaling snapshot vote is used to capture the sentiment of all STAKE holders. We also plan to potentially prepare multiple signaling snapshot votes to capture community sentiment as much as possible.

Technically STAKE holders cannot stop the swap from happening if GnosisDAO decides to create the swap contract. However, going against the xDai community is not in the interest of GnosisDAO.

Currently it is impossible to discern how STAKE holders are feeling about the proposal overall, there is a very vocal group concerned about the conversion rate. How big this group is and what the sentiment is overall amongst STAKE holders will be captured in the snapshot vote.

11. As far as I got it, the validation till SBC will be done as it is now by using Stake in the Validator pools. So the merger will happen when SBC goes live?

The current plan is to merge xDai into the Stake/Gnosis Beacon Chain one week ahead of the ETH mainnet merge. Until then the network will be working as it is working now; secured by POSDAO consensus.

Beacon chain will be launched only with the GNO token so everyone interested to be a validator will need to swap STAKE into GNO once the swap contract is live. The current proposal is that the swap contract will be live for 6 months, however this may be subject to refinement based on tax implications or other concerns. The endpoint/timeline can be changed if there is support and reasoning to extend or shorten the deadline.

12. Who's idea was this - xDai or Gnosis? How much did the Gnosis team pay the xdai team for this? Do they get the same swap value or did they get other monetary compensation as well?

All terms of the proposal are public and published on the Gnosis and xDai forums. xDai team is not receiving any payments or incentives. xDai team members who hold STAKE have the same swap rate as other holders.

xDai team has been looking for investors/partners to support the Eth 2.0 roadmap and accelerate the growth of the chain via new partnerships, marketing, and listings. Gnosis’s investment and partnership can fuel xDai’s expansion by helping the chain grow and optimize its ecosystem and increase its community.

13. Incentive programs using STAKE, like on Agave, have really helped push liquidity to projects and have helped positively increase mindshare for xdai as a whole. Would there be replacement incentive programs to take place for those done with STAKE to now use GNO instead?

There will definitely be some incentives programs from the GNO side, with a much larger infusion of incentives than have occurred previously. Lack of liquidity has been an ongoing issue for DEXs and other projects deploying on xDai, and has led to users fleeing to other chains with higher liquidity. Referencing the current proposal, GnosisDAO will reserve 400k GNO (~$190 million) to develop the Gnosis Chain ecosystem and incentivize usage.

14. Which network in your opinion would benefit the most with the merge? xDai or Gnosis?

Our hope is that both orgs, along with users of the new chain, will benefit. In this alliance based on merged branding and shared tokenomics, marketing will increase, incentives and liquidity will increase, more projects will deploy and greater alignment with the Eth2 ecosystem will be achieved. The xDai team will remain autonomous but have access to more resources, and the Gnosis team will benefit by expanding into a comprehensive & scalable environment.

15. Which unique aspects of the counterparty's chain do you value the most?

xDai: Gnosis safe has been a huge benefit to the blockchain space. So many projects and DAOs use it for multi-sig governance. Looking forward, Circles may prove to be something that goes beyond blockchain to help level the playing field for society with a Universal Basic Income. It’s a huge idea and one that Gnosis is committed to. It’s very exciting and potentially life-changing for many people.

Gnosis: xDai has been committed to building excellent technology that makes Ethereum compatibility scaleable from the get go and is fully aligned with the Gnosis values of fostering network effects without locking users in. Both xDai and Gnosis believe in the power of decentralized technology to empower individuals. However, with the gas price development on Eth1 as it stands, the once very inclusive Ethereum needs compatible layer ones to not price out all users but the biggest whales. To us, xDai is that solution.

16. I would like to know why Gnosis? In addition to providing money, Gnosis has other ways to raise the STAKE ecosystem? Who will be the CEO after the merger? Will the STAKE team stay in the new company? Does the merger affect the original ecosystem projects - for example SUSHI?

In addition to providing money, Gnosis has other ways to raise the STAKE ecosystem?

A new BizDev unit will be established to drive business development and marketing activities of the Gnosis Chain. Such activities will include attracting well-performing and well-known multi-chain protocols to launch on the Gnosis Chain. Gnosis Chain will cover the costs associated with such deployments. A new marketing unit will also be implemented to drive marketing activities of the Gnosis Chain.

Who will be the CEO after the merger? Will the STAKE team stay in the new company?

GnosisDAO (the entity governed by GNO holders that holds Gnosis assets) does not have a CEO. The CEO for Gnosis the company will continue to be Martin. Igor will remain the "CEO" of xDai. Both entities will render services to the Gnosis\DAO.

How do both teams (xDAI and Gnosis) see a successful cooperation in the time after the merger? Will team members be swapped or maybe leave?

There are no organizational changes planned in the xDai core and dev teams. RnD teams in both organizations will remain autonomous. New autonomous units will be created for BizDev and Marketing. All dev talents on the xDai team will be encouraged to stay.

Does the merger affect the original ecological project? For example SUSHI?

GnosisDAO can consider adding liquidity to the various DeFi protocols on the xDAI chain to support their adoption using the 400k GNO (~$190 million) fund reserved for that purpose.

17. How do you imagine attracting new dev talents to the chain?

Gnosis team has a well-defined and successful recruiting process and is committed to help hire new developers for the chain and other associated products. Additional units such as BizDev and Marketing will be established to drive adoption of Gnosis chain including a push to hire top talent.

18. Will you keep the goals (becoming an official ETH testnet with real value in stake) of xDai?

Gnosis Chain will continue xDai’s intent to follow the Ethereum roadmap as closely as possible. Future goals include:

  • Offer the highest degree of compatibility between Gnosis Chain and Ethereum
  • Set up a Gnosis Beacon Chain (in preparation of a later merge)
  • Develop over time a role similar to what Kusama is to Polkadot

· One min read
Archive Post

This post is more than one year old. The information may be outdated. Check the latest posts.

Weekly Newsletter


In-depth weekly highlights are on Substack. You can sign up to receive in your email or view the newsletter anytime without signing up.

📰Weekly News for October 29:

Tweets of the Week

Follow xDai on Twitter for regular news and updates

· One min read
Archive Post

This post is more than one year old. The information may be outdated. Check the latest posts.

Weekly Newsletter


In-depth weekly highlights are on Substack. You can sign up to receive in your email or view the newsletter anytime without signing up.

📰Weekly News for October 22:

Tweets of the Week

Follow xDai on Twitter for regular news and updates