> For the complete documentation index, see [llms.txt](https://cardanoupgrades.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-faq.md).
# Dijkstra upgrade FAQ
The hard fork working group has collated key questions and formed the following frequently asked questions (FAQ) for the benefit of the community.
## **Questions for ada holders**
Will there be token migration required due to the hard fork?
No, there will be no token migration required as part of the Dijkstra era hard fork. The fork is a protocol update that will be implemented automatically across the network. All ADA tokens will remain fully accessible and functional before, during, and after the hard fork without any need for token migration. However, you should ensure that your wallet and any tools you are using are up-to-date with the latest version to support any new features or improvements introduced by the fork.
What should token holders on-chain and those with staked tokens do?
For token holders, whether on-chain or staked, there is no specific action required on your part. Your tokens will remain safe and fully functional. However, you should ensure that your wallet and any tools you are using are up-to-date with the latest version to support any new features or improvements introduced by the fork.
***
## **Questions on the general van Rossem hard fork**
Cardano Testnet Definitions
Cardano Test Network Definitions
**SanchoNet Testnet**
* Community run network originally for governance testing but now used for testing interesting scenarios not possible on other networks
* Potential to see untested and unreleased node versions
* Specifications
* Very small number of community stake pools \~10
* Varied configurations
* Varied Protocol Parameters
* Expectations
* No guarantees of uptime
* No guarantees of support -- community run
* No guarantees of upgrade readiness
**Preview Testnet**
* Aimed to be a move fast break things environment
* Tends to be long living, but significant rollbacks and truncations are to be expected
* Upgrade readiness: \~one week adoption window given ahead of hard forking
* Specifications
* Protocol Parameters close to mainnet -- epoch lengths (1 day)
* Small set of stake pools, primarily operated by founding entities
* Configurations close to mainnet
* Expectations
* No guarantees of uptime -- move fast break things
**PreProd Testnet**
* Aimed to be on close parity with Cardano Mainnet, long living testnet
* Upgrade readiness: \~six week adoption window given ahead of hard forking
* Specifications
* Protocol Parameters matching Cardano mainnet
* Large set of stake pool operators
* Configurations matching mainnet
* Expectations
* Uptime aimed to be close to mainnet
What is a GA?
A governance action (GA) is a proposed on-chain change to Cardano. The various voting groups vote on it, as described within [CIP-1694 Governance Actions](https://github.com/cardano-foundation/CIPs/blob/master/CIP-1694/README.md#governance-actions).
How do I know which governance actions are real?
It is encouraged to review and read all governance actions carefully, anyone within the community can raise a governance action for consideration.
All governance actions raised by Intersect, on behalf of the community, will be clearly sign posted and the metadata hosted on the Intersect GitHub repository.
Who can vote on these GAs?
Cardano mainnet is currency within governance bootstrapping, this means the governance model is not fully activated.
In this bootstrapping phase only the CC and the SPOs can vote on governance actions accordingly. This is detailed in CIP-1694 bootstrap phase and interim consitution.
Whats in the scope for Dijkstra era hard fork?
***
## Questions on the Hard Fork working group
The Hard Fork Working Group's role in Cardano Upgrades
The hard fork working group is spun up to help coordinate Cardano's upgrades, with oversight from Intersect's Technical Steering Committee.
The working group aims to be a transparent place to
* discuss upgrades
* track ecosystem readiness
* make decisions on the submission on hard fork initation governance actions
Intersect staff help this effort by organising the meetings, writing up meeting minutes, publishing communications and reaching out to stakeholders.
How often does the hard fork working group meet?
The group meets weekly in the lead-up to a hard fork.
How can the community get involved in the hard fork working group?
Join the dedicated Upgrade Discord channel at [#wg-hard-fork](https://discord.com/channels/1136727663583698984/1242097284619960411) (on the Intersect Discord server). This channel is monitored by the working group, with updates being shared and questions answered. Alternatively, you can reach out to
The hard fork working group meetings are in the shared [Luma Calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif). The [Cardano Upgrades GitBook](https://cardanoupgrades.docs.intersectmbo.org/) contains important hard fork context, working group policies, readiness tracking, and working group meeting minutes.
***
## **Questions on Testing and Development**
How will the Dijkstra era hard fork be previewed and tested before full deployment?
Node with protocol version 12 will be previewed and tested on [preview and pre-production testnets](https://docs.cardano.org/cardano-testnets/environments/). This process is controlled by the community, ensuring thorough testing and validation before the full deployment.
How does the community involvement in testing work?
Community testing is conducted on test networks with the latest node versions, where various elements including plutus built-ins for example, can be tested. This stage allows for community feedback and is essential for ensuring the robustness of the hard fork.
What is the role of stake pool operators upgrading to the latest node for the Dijkstra era hard fork?
Stake Pool Operators play an important (the most important!) part in any hard fork. The community requires them to upgrade prior to a hard fork combinator event. The latest status of SPOs' readiness can be found on our [Dijkstra Upgrade Readiness page](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/dijkstra-upgrade-readiness).
Is there a node version that can be used for testing?
***
## Questions on how to get involved and how to prepare
How will changes and updates be communicated to the community?
Updates and significant changes will be communicated through various channels including [X](https://x.com/intersectmbo), [Discord](https://discord.com/channels/1136727663583698984/1262393547915657287), and the project’s [upgrade space](https://cardanoupgrades.docs.intersectmbo.org/). Important updates will also be discussed in follow-up meetings, ensuring all stakeholders have the latest information and can provide feedback.
Meeting minutes and action items from all hard fork working group meeting can be found at this [link](https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/hard-fork-working-group-meeting-minutes).
What role does community governance play in the Cardano upgrade roadmap?
Community governance is a central aspect of Cardano’s upgrade roadmap. Through different initiatives and delegated representatives (DReps) the community actively participates in decision-making processes, shaping the future direction of the network.
What steps should users take to prepare for the hard fork?
**Here’s what users can do to prepare:**
* **Join** the dedicated Upgrade Discord channel at [#wg-hard-fork](https://discord.com/channels/1136727663583698984/1242097284619960411) (on the Intersect Discord server). This channel is monitored by the working group, with updates being shared and questions answered. Alternatively, you can reach out to
* The hard fork working group meetings are in the shared [Luma Calendar](https://luma.com/calendar/cal-TMjYNpSY4huYYif) along with the newly started X spaces for the next several weeks. The [Cardano Upgrades GitBook](https://cardanoupgrades.docs.intersectmbo.org/) contains important hard fork context, working group policies, readiness tracking, and working group meeting minutes.
* To further increase reach, the group began to hold regular X spaces each Thursday.
* **Update wallets and applications** - Ensure you’re using the latest versions of [Cardano wallets](https://docs.cardano.org/new-to-cardano/types-of-wallets/) and applications to guarantee compatibility with the new protocol.
* **Take part in testing -** This is especially true for Cardano Preview testnet where you can test the tools and improvements that are brought with van Rossem hard fork.
***
If you find any information on this page incorrect or misleading please email and request a correction.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cardanoupgrades.docs.intersectmbo.org/dijkstra-era-upgrade/dijkstra-upgrade-faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.