Skip to content

Conversation

@spooktheducks
Copy link
Contributor

No description provided.

@netlify
Copy link

netlify bot commented Jul 28, 2025

Deploy Preview for alloradocs ready!

Name Link
🔨 Latest commit 98b948f
🔍 Latest deploy log https://app.netlify.com/projects/alloradocs/deploys/68a7a67a3f1ba2000847373b
😎 Deploy Preview https://deploy-preview-132--alloradocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@amimart amimart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made some remarks about slight imprecisions

Comment on lines 86 to 87
**URL Components**:
- **`v7`**: Latest network version number
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**URL Components**:
- **`v7`**: Latest network version number
**URL Components**:
- **`v9`**: Latest emissions API version number

The latest version is v9, and it is not exactly related to the network version but more precisely the emissions module API version.

### Fee Structure Update

__`fees Xuallo` becomes `gas-prices 10uallo`__
**`fees Xuallo` becomes `gas-prices 10uallo`**
Copy link
Contributor

@amimart amimart Jul 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way we specify gas related options actually didn't change since the integration of x/feemarket, this module only brings a variable gas price computed on-chain, the current gas price can be queried with allorad q feemarket gas-prices.

Even with this EIP-1559 implementation we can specify --gas auto which will try to estimate gas usage, or use --fees Xuallo to set a limit to the gas fees to spend on a tx.

- **Coordination mechanism**: Synchronize complex upgrades across the network

#### For Allora Chain Developers
## Developer Upgrade Procedures
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is worth detailing how to implement an upgrade in the chain codebase, this doesn't concerns validators
cc @xmariachi

### Truth Relay
#### Truth Relay Architecture

Below is a sample structure of what your `main.go`, `main.py` and Dockerfile will look like. You can also find a working example [here](https://github.com/allora-network/basic-coin-prediction-node).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably want to revamp or remove this old repo

- consolidate fragmented get-started guides into streamlined quick-start and network-interaction
- remove outdated separate guides
- update navigation structure across all documentation sections
- refresh content in consumer, reputer, SDK, validator, and topic-creator docs
- add comprehensive topics list (29 active topics) to networking guides
- add new sample-projects section to home
- add better CLI examples and best practices
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants