Skip to content

Docs fix #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/devs/get-started/managing-gas.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ import { Callout } from 'nextra/components'

# Managing Gas with `allorad`

Invoking transactions causes network validators to do computations on your behalf and update the chain's state. These actions are compensated via _gas_. Gas is paid by wallets who send transactions to the Allora chain.
Invoking transactions causes network validators to do computations on your behalf and update the chain's state. These actions are compensated via _gas_. Gas is paid by wallets that send transactions to the Allora chain.

In its [v0.7.0 release](https://github.com/allora-network/allora-chain/releases/tag/v0.7.0), Allora incorporated the [x/feemarket module](https://github.com/skip-mev/feemarket), which means that gas calculations follow an [EIP-1559-like schedule](https://help.coinbase.com/en/coinbase/getting-started/crypto-education/eip-1559) (see: the [original EIP-1559](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1559.md)). This requires transactions to be structured differently from other cosmos chains.

Expand Down
4 changes: 2 additions & 2 deletions pages/devs/get-started/model-forge.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Topics are assigned an ID and categorized by a specific Target Variable, Epoch,
- **Epoch**: A discrete period during which inferences and forecasts are submitted, and rewards are distributed.
- Epochs are defined in blocks on the Network
- Each epoch provides a timeframe for evaluating and scoring the performance of workers and reputers.
- In the Forge Competition, epochs are are abstracted into universal timeframes, e.g. `5min`, `1hr`, `1d`.
- In the Forge Competition, epochs are abstracted into universal timeframes, e.g. `5min`, `1hr`, `1d`.
- **Loss Function**: Measures how far off your model's predictions are from the actual values
- For all topics in the Forge Competition, the loss function is [`Mean Squared Error`](https://en.wikipedia.org/wiki/Mean_squared_error).
- **Metadata**: Additional information about the topic, including the financial indicator, abstracted epoch length, and target variable.
Expand Down Expand Up @@ -148,4 +148,4 @@ Steps:
3. Click on a topic to view your performance metrics

![topic-metrics](/topic-stats.png)
- Your `Score` and `ALLO Earned` indicate your overall performance in the topic.
- Your `Score` and `ALLO Earned` indicate your overall performance in the topic.