FAQ
Common questions when using Phalcon Fork
Fork Related
How to create a Fork
Creating a Fork is straightforward. Click the button in the Fork list to create a Fork. Also, a REST API can be used to create a Fork.
How to delete a Fork
To delete a Fork, access its Settings.
Click the button to delete a Fork. Also, a REST API is available to delete a Fork.
Be cautious; deleting a Fork will remove all the data inside a Fork and cannot be recovered.
Transactions Related
How to simulate transactions inside a Fork
Sending a transaction can be done through the GUI interface or Fork RPC.
Development Framework Related
How to get the necessary API keys and IDs for integration
When integrating Phalcon Fork into development frameworks, a couple of API keys and IDs are needed. This page shows the method to obtain such IDs.
API Key
The API key is used to verify contracts and manipulate projects and Forks. It's available in the API section of the BlockSec account.
Do NOT share this key with others.
Project ID
The project ID can be found inside the Project Setting, shown at the bottom of the project list.
Fork ID and RPC ID
The Fork ID denotes a Fork, and the RPC ID denotes the RPC used to access the Fork. They are available in Settings inside a Fork.
Fork RPC
The FORK_RPC
is shown in the settings inside a Fork. It is also shown in the Fork details.
Why do I get a 'nonce too high' message
When simulating transactions inside a Fork using Foundry, it returns the 'nonce too high` error message. What should I do?
It's because the transactions sent to Fork are too fast. Add an --slow
option to the command line. See the Foundry book for more information.
--slow:
Makes sure a transaction is sent only after its previous one has been confirmed and succeeded.
How to debug methods invocation in Fork RPC
Sometimes, the result is unexpected when using some scripts to interact with Fork RPC. In this case, we want to debut the methods invoked on the Fork RPC and the return values.
We can use the following Python script to sit between the local script and the remote Fork RPC to see the parameters and return values.
Last updated