Shekyl Stats

Refreshing...

Network

Connected
Seed Nodes Active
--

Chain

Current Block
0
Target Height
0
Top Block Hash
--
Block Time Target
2 min

Rewards

Last Block Reward
0.000000 SKL
Difficulty
0
Estimated Hash Rate
0 H/s

Supply

Circulating Supply
--
Remaining Supply
--
Total Burned
0.000000 SKL

Economics

Release Multiplier
0
Burn Rate %
0

Staking

Stake Ratio
0
Staker Pool
0.000000 SKL
Staker Emission Share
0
Total Staked
N/A
Staking Height
N/A
Tier 0 Lock Blocks
N/A
Tier 1 Lock Blocks
N/A
Tier 2 Lock Blocks
N/A

Protocol

Transaction Format
TransactionV3
Membership Proof
FCMP++
Spend Auth
Ed25519 + ML-DSA-65
Confidentiality
Stealth + BP+
Learn more about the technology →

Node

TX Pool Size
0
Database Size
0 B
Node Version
--
Sync Status
Syncing

Contributing

Shekyl is open source. Here's how to get involved.

Get Started

Active development on dev

Major work in progress — Rust wallet engines, BIP-39 recovery, LWMA-1 difficulty, and staking shard visualization — lands on the dev branch first. Stable releases, downloads, and the documentation browser here track main.

Stable docs on main →Follow active development

GitHub Repository

Browse stable source on main, fork the project, and submit pull requests.

View on GitHub →

Development Branch

Follow in-flight work: Rust wallet engines, BIP-39, LWMA-1, and staking features land here first.

Browse dev branch →

Report a Bug

Found an issue? Open a GitHub issue with a clear description of the problem.

Open an Issue →

Documentation

Technical specs, protocol references, and contributor guides on main.

Read the Docs →

Get in Touch

Questions or ideas? Reach the maintainers by email.

Email →

Contribution Guidelines

Shekyl follows the C4 (Collective Code Construction Contract) process, a proven collaboration model for open-source projects.

Patch Requirements

  • Patches should be self-contained — one patch per issue, feature, or logical change.
  • Follow the code style of the chunk you are modifying.
  • A patch must compile cleanly and pass project self-tests on the principle target platform.
  • Commit messages should have a concise subject line (under 50 characters) with an optional longer body.
  • PGP signing of commits is strongly encouraged.

Pull Request Process

  1. Fork the repository and work on your fork
  2. Rebase your branch before submitting — no merge commits
  3. Create a pull request back to the project
  4. Maintainers review using the platform interface; PRs remain open for at least 168 hours (1 week) unless urgent
  5. A new contributor who makes a correct patch is invited to become a Maintainer

Licensing

Shekyl uses the BSD-3-Clause license. All contributions use the same license as the project. Patches are owned by their authors — there is no copyright assignment process.

Key Principles

  • • Copyrights are owned collectively by all contributors
  • • Everyone has an equal right to become a contributor
  • • Contributors are responsible for identifying themselves in the contributor list
Back to About