Skip to content

Add Redmansion Chain (chainId: 192) #7572

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: master
Choose a base branch
from

Conversation

redmansionorg
Copy link

Redmansion Chain (ChainID: 192)

This PR adds metadata for Redmansion Chain, a new EVM-compatible public chain focused on literary creation, copyright registration, and royalty distribution for Web3-native authors and artists.

The chain is fully operational, publicly accessible, and includes:

🟢 Public RPC Endpoint: https://redmansion.io/srpc/

🔍 Explorer: https://redmansion.io

🌐 Website / For Creator: https://www.redmansion.io

📦 GitHub: https://github.com/redmansionorg

Chain Overview and Project Summary for Redmansion Chain.txt

🧠 OpenTimestamp-integrated consensus

🖼️ Official logo (PNG, 256x256, included in this PR)

📚 Chain Overview and Project Summary for Redmansion Chain

The chain is deployed, actively maintained, and already in use for NFT-based novel and artwork publishing.

Please let us know if further information is required. Thank you for maintaining this great list!

Copy link

github-actions bot commented Aug 1, 2025

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

@Alex012026
Copy link

Hi maintainers,

First-time contributor — the workflows are currently pending approval. I've followed the contribution guidelines and everything should be correctly set up. Kindly approve the CI when possible.

The chain is already deployed and in public use. All endpoints (RPC + Explorer) are online and available into Chain list too. Kindly

Add chain with ID 347 (Kross Network Mainnet) and above one too.

Please find the details for chain with ID 347 below:

This PR adds eip155-347.json for Kross Network.

ref: #7579

Chain ID: 347
Name: Kross Network Mainnet
Symbol: KSS
RPC: https://rpc-v1.kross.network/
Icon: kross (IPFS-based, defined in _data/icons/kross.json)
Thank you!

@recmo @FrederikBolding

@redmansionorg
Copy link
Author

Hi maintainers 👋

This is a first-time PR to add Redmansion Chain (ChainID: 192) — a live, EVM-compatible network focused on decentralized novel and copyright publishing.

The chain is already deployed and in public use. All endpoints (RPC + Explorer) are fully online and conform to Chainlist schema.

🙏 Since this is a first-time contribution, the CI workflows are currently awaiting manual approval.
Could you please help approve the workflows so the checks can run?

Thanks so much for maintaining this important repo, and let us know if any info is missing.

@recmo @FrederikBolding

@redmansionorg
Copy link
Author

Branch updated with latest master to ensure no conflicts. Waiting for workflow approval.

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.

2 participants