Update v0.3.0 public release documentation
This commit is contained in:
parent
9547d4a791
commit
3577ef7e8c
SSH key fingerprint:
SHA256:739BZv8LvIDY2tR7lXLy/IQ6MaGTQtYcG9GNvCjmpVM
3 changed files with 293 additions and 55 deletions
156
README.md
156
README.md
|
|
@ -2,25 +2,38 @@
|
|||
|
||||
Vexta Core is the reference implementation of the Vexta blockchain.
|
||||
|
||||
Vexta is an open-source, UTXO-based proof-of-work cryptocurrency built on the Bitcoin Core architecture. It uses a single SHA256D mining algorithm, ten-minute target block times, and a Bitcoin-style subsidy halving schedule.
|
||||
Vexta is an open-source, UTXO-based proof-of-work cryptocurrency built on the Bitcoin Core architecture. Vexta uses a multi-algorithm proof-of-work system combining **SHA256D** and **RandomX** on a single blockchain.
|
||||
|
||||
> **Early development software**
|
||||
>
|
||||
> Vexta Core v0.1.0 is an initial public release. Network parameters, software behavior, and compatibility requirements may still change. Back up wallets before testing and do not use funds you cannot afford to lose.
|
||||
## Vexta Core v0.3.0
|
||||
|
||||
Vexta Core v0.3.0 introduces Vexta's multi-algorithm mining architecture.
|
||||
|
||||
RandomX activates on mainnet at **block 8,099**. SHA256D remains fully supported, with both algorithms sharing the same blockchain, transactions, addresses, block rewards, and consensus history.
|
||||
|
||||
Each mining algorithm maintains its own difficulty while contributing normalized chainwork to the same chain.
|
||||
|
||||
### Mining Algorithms
|
||||
|
||||
| Algorithm | Type | Status |
|
||||
|---|---|---|
|
||||
| SHA256D | ASIC-oriented proof of work | Active |
|
||||
| RandomX | CPU-oriented proof of work | Activates at block 8,099 |
|
||||
|
||||
The network targets an average **10-minute global block interval** across both algorithms.
|
||||
|
||||
## Download
|
||||
|
||||
The latest Windows and Linux builds are available from the GitHub Releases page:
|
||||
Official Windows and Linux builds are published on the GitHub Releases page:
|
||||
|
||||
[Download Vexta Core v0.1.0](https://github.com/VextaProject/vexta/releases/tag/v0.1.0)
|
||||
https://github.com/VextaProject/Vexta/releases
|
||||
|
||||
Available packages:
|
||||
Vexta Core v0.3.0 release packages:
|
||||
|
||||
- Windows x86-64 portable ZIP
|
||||
- Linux x86-64 portable TAR.GZ
|
||||
- SHA-256 checksum files for both packages
|
||||
- `vexta-v0.3.0-linux64.tar.gz`
|
||||
- `vexta-v0.3.0-linux64-gui.tar.gz`
|
||||
- `vexta-v0.3.0-win64.zip`
|
||||
|
||||
Always verify the downloaded archive against its accompanying checksum file.
|
||||
Always verify downloaded release files against the SHA-256 checksums published with the release.
|
||||
|
||||
## Included Programs
|
||||
|
||||
|
|
@ -33,28 +46,93 @@ Always verify the downloaded archive against its accompanying checksum file.
|
|||
| `vexta-tx` | Raw transaction utility |
|
||||
| `vexta-util` | General Vexta utility |
|
||||
|
||||
## Links
|
||||
|
||||
- [Discord](https://discord.gg/zzpm7ghN3e)
|
||||
|
||||
## Network Parameters
|
||||
|
||||
- Name: Vexta
|
||||
- Ticker: VTX
|
||||
- Consensus: Proof of Work
|
||||
- Mining algorithm: SHA256D
|
||||
- Target block time: 10 minutes
|
||||
- Initial block reward: 50 VTX
|
||||
- Subsidy halving interval: 210,240 blocks
|
||||
- SegWit: Enabled
|
||||
- Taproot: Enabled
|
||||
- URI scheme: `vexta:`
|
||||
- **Name:** Vexta
|
||||
- **Ticker:** VTX
|
||||
- **Consensus:** Proof of Work
|
||||
- **Mining algorithms:** SHA256D + RandomX
|
||||
- **RandomX mainnet activation:** Block 8,099
|
||||
- **Target block time:** 10 minutes globally
|
||||
- **Initial block reward:** 50 VTX
|
||||
- **Subsidy halving interval:** 210,240 blocks
|
||||
- **SegWit:** Enabled
|
||||
- **Taproot:** Enabled
|
||||
- **URI scheme:** `vexta:`
|
||||
- **P2P port:** 19333
|
||||
- **RPC port:** 19332
|
||||
|
||||
## Multi-Algorithm Mining
|
||||
|
||||
Vexta uses two independent proof-of-work algorithms on one blockchain.
|
||||
|
||||
SHA256D and RandomX blocks:
|
||||
|
||||
- share the same chain
|
||||
- use the same transaction set and address system
|
||||
- receive the same block subsidy rules
|
||||
- maintain separate per-algorithm mining difficulty
|
||||
- contribute normalized proof of work to the common chain
|
||||
|
||||
This allows different classes of mining hardware to participate without separating Vexta into independent chains.
|
||||
|
||||
## RandomX
|
||||
|
||||
RandomX is integrated as Vexta's second proof-of-work algorithm.
|
||||
|
||||
The implementation uses algorithm-aware block validation, independent RandomX difficulty tracking, deterministic RandomX seed selection, and normalized chainwork accounting.
|
||||
|
||||
Mainnet RandomX activation occurs at block **8,099**.
|
||||
|
||||
## Difficulty Adjustment
|
||||
|
||||
Vexta uses algorithm-aware difficulty handling so SHA256D and RandomX can respond independently to changes in mining power while remaining part of the same chain.
|
||||
|
||||
The network continues to target an average global block interval of approximately 10 minutes.
|
||||
|
||||
## Post-Quantum Development
|
||||
|
||||
Vexta Core also includes post-quantum wallet and address functionality developed as part of the project's longer-term cryptographic security work.
|
||||
|
||||
Multi-algorithm proof of work and post-quantum wallet functionality are separate parts of the Vexta architecture.
|
||||
|
||||
## Explorer
|
||||
|
||||
Official Vexta blockchain explorer:
|
||||
|
||||
https://vextaproject.org/explorer/
|
||||
|
||||
## Whitepaper
|
||||
|
||||
Official Vexta whitepaper:
|
||||
|
||||
https://vextaproject.org/whitepaper.pdf
|
||||
|
||||
## Mining
|
||||
|
||||
Official Vexta mining pool:
|
||||
|
||||
https://vexta-pool.co.uk
|
||||
|
||||
## Community
|
||||
|
||||
Discord:
|
||||
|
||||
https://discord.gg/zzpm7ghN3e
|
||||
|
||||
Official website:
|
||||
|
||||
https://vextaproject.org
|
||||
|
||||
## Data Directory
|
||||
|
||||
Vexta Core uses a separate data directory and configuration from DigiByte Core.
|
||||
Vexta Core uses its own data directory and configuration.
|
||||
|
||||
The default configuration filename is `vexta.conf`.
|
||||
The default configuration filename is:
|
||||
|
||||
```text
|
||||
vexta.conf
|
||||
```
|
||||
|
||||
## Building from Source
|
||||
|
||||
|
|
@ -62,25 +140,33 @@ Build instructions are available in [INSTALL.md](INSTALL.md).
|
|||
|
||||
Typical Linux build process:
|
||||
|
||||
```bash
|
||||
./autogen.sh
|
||||
./configure
|
||||
make -j"$(nproc)"
|
||||
```
|
||||
|
||||
Project dependencies may also be built using the included `depends` system.
|
||||
Project dependencies can also be built using the included `depends` system.
|
||||
|
||||
Vexta Core v0.3.0 additionally requires RandomX when building the multi-algorithm implementation.
|
||||
|
||||
## Testing
|
||||
|
||||
Run the unit tests with:
|
||||
Unit tests can be built and run using the project test targets.
|
||||
|
||||
make check
|
||||
The Vexta v0.3.0 release was validated with targeted proof-of-work, blockchain, RandomX, multi-algorithm chainwork, difficulty, and block-validation tests.
|
||||
|
||||
Functional tests are located in `test/functional`.
|
||||
Functional tests are located in:
|
||||
|
||||
```text
|
||||
test/functional
|
||||
```
|
||||
|
||||
## Source Code
|
||||
|
||||
Official repository:
|
||||
|
||||
[github.com/VextaProject/vexta](https://github.com/VextaProject/vexta)
|
||||
https://github.com/VextaProject/Vexta
|
||||
|
||||
Release workflow documentation:
|
||||
|
||||
|
|
@ -88,7 +174,11 @@ Release workflow documentation:
|
|||
|
||||
## Contributing
|
||||
|
||||
Contributions are welcome. Changes should prioritize security, stability, compatibility, maintainability, and careful review.
|
||||
Contributions are welcome.
|
||||
|
||||
Changes should prioritize security, stability, compatibility, maintainability, and careful review.
|
||||
|
||||
Consensus changes should be reviewed especially carefully because they can affect compatibility with the live Vexta network.
|
||||
|
||||
## License
|
||||
|
||||
|
|
|
|||
|
|
@ -2,30 +2,118 @@
|
|||
|
||||
## Repositories
|
||||
|
||||
- Private development repository:
|
||||
`~/Projects/vexta`
|
||||
### Private development repository
|
||||
|
||||
Contains the full development history.
|
||||
Push is disabled for all remotes.
|
||||
```text
|
||||
~/Projects/vexta
|
||||
```
|
||||
|
||||
- Public release repository:
|
||||
`~/vexta-public`
|
||||
This repository contains the full Vexta development history.
|
||||
|
||||
Contains only clean public snapshots.
|
||||
This is the only repository allowed to push to GitHub.
|
||||
It is used for development, testing, consensus work, and release builds.
|
||||
|
||||
## Future release process
|
||||
**Never push from this repository.**
|
||||
|
||||
1. Finish and test changes in `~/Projects/vexta`.
|
||||
2. Create release binaries and checksums.
|
||||
3. Copy the current tracked source snapshot into `~/vexta-public`.
|
||||
4. Review the public diff carefully.
|
||||
5. Commit the public snapshot with a release-focused commit message.
|
||||
6. Create a version tag such as `v0.1.1`.
|
||||
7. Push only from `~/vexta-public`.
|
||||
8. Create the GitHub Release and attach binaries and checksum files.
|
||||
### Public release repository
|
||||
|
||||
## Important
|
||||
```text
|
||||
~/vexta-public
|
||||
```
|
||||
|
||||
Never push directly from `~/Projects/vexta`.
|
||||
Never push private phase tags or development branches to the public repository.
|
||||
This repository contains the public Vexta source tree and is the **only repository allowed to push to GitHub**.
|
||||
|
||||
Official GitHub repository:
|
||||
|
||||
https://github.com/VextaProject/Vexta
|
||||
|
||||
## Release Process
|
||||
|
||||
1. Complete development and testing in `~/Projects/vexta`.
|
||||
|
||||
2. Verify that all intended tracked changes are committed.
|
||||
|
||||
3. Build and validate the release binaries.
|
||||
|
||||
4. Generate SHA-256 checksums for all release packages.
|
||||
|
||||
5. Synchronize the public repository from the finalized development commit.
|
||||
|
||||
Example:
|
||||
|
||||
```bash
|
||||
cd ~/vexta-public
|
||||
git fetch ~/Projects/vexta <release-branch>
|
||||
git checkout -B <public-release-branch> FETCH_HEAD
|
||||
```
|
||||
|
||||
6. Review the complete public diff and repository status.
|
||||
|
||||
7. Update public documentation, including:
|
||||
|
||||
- `README.md`
|
||||
- `RELEASE_WORKFLOW.md`
|
||||
- release notes
|
||||
- other release documentation when required
|
||||
|
||||
8. Commit the final public release state.
|
||||
|
||||
9. Create the Vexta release tag.
|
||||
|
||||
Vexta release tags use the format:
|
||||
|
||||
```text
|
||||
vexta-vX.Y.Z
|
||||
```
|
||||
|
||||
Example:
|
||||
|
||||
```text
|
||||
vexta-v0.3.0
|
||||
```
|
||||
|
||||
10. Verify that the release tag points to the intended release commit.
|
||||
|
||||
11. Push the release branch and Vexta release tag to GitHub **only from `~/vexta-public`**.
|
||||
|
||||
12. Create the GitHub Release.
|
||||
|
||||
13. Attach the official release archives and publish their SHA-256 checksums.
|
||||
|
||||
14. Verify the published source, tag, release files, and checksums before announcing the release.
|
||||
|
||||
## Release Validation
|
||||
|
||||
Before publishing a release, verify:
|
||||
|
||||
- the public tracked tree contains only intended changes
|
||||
- the release commit is correct
|
||||
- the Vexta release tag points to the correct commit
|
||||
- Linux binaries report the intended Vexta Core version
|
||||
- Windows binaries report the intended Vexta Core version
|
||||
- required consensus and proof-of-work tests pass
|
||||
- release archives contain the expected binaries
|
||||
- SHA-256 checksums match the final release archives
|
||||
|
||||
## Important Rules
|
||||
|
||||
Never push directly from:
|
||||
|
||||
```text
|
||||
~/Projects/vexta
|
||||
```
|
||||
|
||||
Never expose private development branches, private tags, temporary build files, or unrelated untracked files through the public repository.
|
||||
|
||||
Never use destructive cleanup commands such as `git clean` in the private development repository unless the contents have been reviewed explicitly.
|
||||
|
||||
Only push Vexta public releases from:
|
||||
|
||||
```text
|
||||
~/vexta-public
|
||||
```
|
||||
|
||||
Release tags should use the Vexta-specific naming convention:
|
||||
|
||||
```text
|
||||
vexta-vX.Y.Z
|
||||
```
|
||||
|
|
|
|||
60
doc/vexta-v0.3.0-release-notes.md
Normal file
60
doc/vexta-v0.3.0-release-notes.md
Normal file
|
|
@ -0,0 +1,60 @@
|
|||
# Vexta Core v0.3.0
|
||||
|
||||
## Major Network Upgrade: Multi-Algorithm Mining
|
||||
|
||||
Vexta Core v0.3.0 introduces **RandomX** as a second proof-of-work algorithm alongside **SHA256D**.
|
||||
|
||||
RandomX activates on Vexta mainnet at **block 8,099**.
|
||||
|
||||
After activation:
|
||||
|
||||
- SHA256D remains fully supported
|
||||
- RandomX becomes available as the second mining algorithm
|
||||
- both algorithms mine the same Vexta blockchain
|
||||
- both use the same transactions, addresses, and block reward rules
|
||||
- each algorithm maintains its own mining difficulty
|
||||
- both contribute to the same chain through normalized chainwork
|
||||
|
||||
The network continues to target an average global block interval of approximately **10 minutes**.
|
||||
|
||||
## Upgrade Notice
|
||||
|
||||
Node operators, mining pools, exchanges, explorers, and other infrastructure should upgrade to **Vexta Core v0.3.0** before block **8,099**.
|
||||
|
||||
Existing SHA256D mining remains supported after activation.
|
||||
|
||||
## RandomX
|
||||
|
||||
RandomX expands Vexta mining beyond SHA256D ASIC hardware and adds a CPU-oriented mining option directly to the same network.
|
||||
|
||||
RandomX proof-of-work is integrated into Vexta consensus while preserving the existing Vexta blockchain, transaction system, addresses, and block reward rules.
|
||||
|
||||
## Multi-Algorithm Difficulty
|
||||
|
||||
SHA256D and RandomX maintain separate mining difficulty histories so each algorithm can respond independently to changes in its own mining power.
|
||||
|
||||
Both algorithms remain part of the same best-chain selection process through normalized chainwork.
|
||||
|
||||
## Post-Quantum Functionality
|
||||
|
||||
Vexta Core v0.3.0 retains the project's existing post-quantum wallet and address functionality.
|
||||
|
||||
Post-quantum functionality and multi-algorithm proof-of-work are separate parts of the Vexta architecture.
|
||||
|
||||
## Official Links
|
||||
|
||||
Website:
|
||||
|
||||
https://vextaproject.org
|
||||
|
||||
Blockchain explorer:
|
||||
|
||||
https://vextaproject.org/explorer/
|
||||
|
||||
GitHub:
|
||||
|
||||
https://github.com/VextaProject/Vexta
|
||||
|
||||
Discord:
|
||||
|
||||
https://discord.gg/zzpm7ghN3e
|
||||
Loading…
Reference in a new issue