✝ Living vision · Current application · Responsible growth

Build technology that points beyond itself.

Jesus Christ Saves Token is a Christ-centered, non-custodial XRP Ledger project. Its purpose is to make prayer, testimony, Scripture, public verification, and practical Christian service easier to encounter and preserve—without treating a token, NFT, application, or social platform as a substitute for Jesus Christ, Scripture, prayer, fellowship, church, pastoral care, or personal responsibility.

Enter Sign the Ledger Explore JCS Fellowship Inspect public XRPL data
Vision 3.0.0 XRPL Mainnet Non-custodial Public evidence · private dignity

The message comes first

Technology is a vessel, not the destination.

The written vision is complete without audio or video. The optional message player is not loaded until you choose to load it, reducing automatic third-party requests, saving bandwidth, and allowing discreet reading when sound or media could create risk.

Nothing on this page asks you to hold JCS, connect a wallet, mint an NFT, or make a transaction before reading the mission.

Loading the player contacts YouTube’s privacy-enhanced domain. The video does not autoplay and sound remains under your control.

Vision and core values

This is a living statement of intent and responsibility. It is not a technical white paper, securities offering, promise of profit, church charter, or claim of spiritual authority.

Christ first · technology second

The mission is Christ; the technology is a tool. JCS exists to carry testimony about Jesus, preserve prayer and Scripture references in durable digital form, support voluntary fellowship, and make public project activity easier to verify.

Every system should protect human dignity, disclose its limitations, minimize private-data exposure, preserve user-controlled authorization, and remain useful even to a visitor who never buys, holds, or trades JCS.

Christ centered

Features should direct attention toward Jesus Christ rather than speculation, personalities, or technological novelty.

Human dignity

Prayer, grief, crisis, disability, poverty, persecution, and testimony must never become engagement bait.

Voluntary participation

No prayer, testimony, NFT, transaction, reaction, or public record should occur without a deliberate user action.

Non-custodial design

Users review and authorize through Xaman. The website must never request a seed phrase, private key, or wallet passcode.

Public transparency

The issuer, token identity, AMM, order books, transactions, and public records should be independently inspectable.

Privacy restraint

Public evidence should contain the minimum necessary information. Sensitive communication belongs off the public ledger.

Accessible witness

Core text should remain usable without sound, animation, a wallet, a token balance, or a high-powered device.

Stewardship over hype

Utility, truth, maintenance, safety, and service take priority over unsupported price, adoption, or partnership claims.

What exists now

JCS is already more than a token landing page, but the current deployment is still primarily a static, client-side application. Live functions and future concepts are separated so visitors can tell what is present from what remains planned.

Current application surfaces
Live

JCS faith and XRPL portal

Scripture, sacred media, Xaman-authorized interactions, JCS/XRP market information, and non-custodial transaction review.

Open JCS Home
Live

Sign the Ledger

Prayer NFTs, public testimony records, replies, Amen reactions, and explicit Xaman authorization.

Open Sign the Ledger
Live

Prayer and Integrity Map

A read-oriented visualization using public XRPL information without requesting wallet secrets.

Open Prayer Map
Live

Identity and discovery

Canonical domain, Web DID, XRP Ledger TOML, AI manifest, sitemap, robots policy, and public source history.

Open DID document
Live

Privacy, terms, and security

Dedicated policies for public-ledger privacy, responsible use, independent services, and vulnerability reporting.

Open Security
Active development

Unified application experience

Shared design, mobile containment, plain-language explanations, metadata consistency, and stronger evidence handling are being applied file by file.

Review repository

JCS Fellowship: the social-platform direction

The long-term objective is a purpose-based Christian community—not a copy of conventional social media built around outrage, follower competition, infinite scrolling, or the sale of attention. The following features are planned product direction, not claims of current deployment.

Planned · not yet fully deployed
Planned

Prayer lifecycle

A request can move from prayer requested, to people committing to pray, to updates, continuing need, respectful closure, or an optional answered-prayer testimony.

Planned

Faith Circles

Small communities for family, local church, Bible study, grief, recovery, veterans, marriage, parenting, ministry projects, and invitation-only prayer.

Planned

Prayer Garden

A symbolic mini-game where prayer, encouragement, updates, Scripture, and acts of service grow a private or shared garden without pay-to-win advantages.

Planned

Scripture Path

Verse-order challenges, passage completion, parable matching, reflection prompts, memory progress, and collaborative reading journeys.

Planned

Acts of Mercy

A privacy-conscious way to offer or request practical help while publishing only the minimum information necessary for safe community response.

Planned

Quiet and Sabbath modes

A finite daily experience with Scripture, a limited number of prayer requests, one act of encouragement, reflection, and a clear stopping point.

No pay-to-pray
No pay-to-be-heard
No token-weighted theology
No wealth-based spiritual rank
No outrage-ranking feed
No deceptive infinite-scroll design
No crisis-post auction or paid priority
No private-data publication by default
No wallet secret collection

Designed for meaningful return, not compulsive return. The proposed experience uses belonging, progress, reciprocity, reflection, and completion as design principles. It should reward prayer, learning, encouragement, and service—not anxiety, comparison, outrage, or financial pressure.

Safety, privacy, and people at risk

Christian expression can carry personal risk. A public blockchain is durable and observable, so technical permanence must never be confused with confidentiality.

Safety before publicity

Silent access

Written Scripture, prayer references, safety guidance, and the mission must remain usable without audio, video, or animation.

Identity restraint

Names, locations, handles, medical details, legal matters, and identifying stories should not be placed on-ledger when disclosure could cause harm.

Public versus private

An NFT or transaction can create public evidence of an event. Private support, pastoral discussion, and sensitive communication require separate protected channels.

Public XRP Ledger transparency

Read-only metrics for the exact JCS issuer and JCS/XRP market. Wallet connection is not required. Every value is a current public-ledger observation or a disclosed calculation.

On demand · validated ledger
Metrics are idle until you choose to load them.

Loading metrics opens a read-only WebSocket connection to a public XRP Ledger server and requests an XRP/USD reference from CoinGecko. No wallet address, prayer, testimony, form entry, or browser identifier is intentionally included in these requests.

Network and evidence status

Validated ledger Not loaded Latest validated sequence reported by the selected server.
Ledger age Not loaded Seconds since the server’s latest validated ledger closed.
Evidence coverage Not loaded Successful source groups divided by the source groups attempted.
Last updated Not loaded Your device time when this report finished.

Issuer settings and distribution sample

Issuer domain Not loaded Decoded from the issuer’s AccountRoot Domain field.
Master key Not loaded Whether the AccountRoot reports the master key as disabled.
Global Freeze Not loaded Current issuer-wide freeze setting.
Clawback Not loaded Whether trust-line clawback authority is enabled.
No Freeze Not loaded Whether individual-freeze authority has been permanently limited.
Require Auth Not loaded Whether trust lines require issuer authorization.
JCS obligations Not loaded Gateway obligations when available; otherwise an observed trust-line sample.
Observed holders Not loaded Positive-balance trust lines in the bounded public sample, not beneficial owners.
Trust lines scanned Not loaded The scan is bounded to reduce public-server load.
Indicative network value Not loaded Not a valuation, appraisal, reserve attestation, or securities market capitalization.

AMM and funded order-book structure

AMM XRP reserve Not loaded Public XRP amount held by the JCS/XRP AMM.
AMM JCS reserve Not loaded Public JCS amount held by the JCS/XRP AMM.
AMM trading fee Not loaded Converted from XRPL fee units of 1/100,000.
AMM spot Not loaded Reserve ratio in XRP per JCS before trade impact.
10 XRP AMM impact Not loaded Constant-product estimate including the configured AMM fee.
Indicative pool value Not loaded Two times the XRP reserve multiplied by the external XRP/USD reference.
Best funded bid Not loaded Highest visible funded bid in XRP per JCS.
Best funded ask Not loaded Lowest visible funded ask in XRP per JCS.
Funded spread Not loaded Bid-ask difference divided by the midpoint.
5% bid depth Not loaded Visible funded XRP demand within 5% of the best bid.
5% ask depth Not loaded Visible funded JCS offered within 5% of the best ask.
Visible makers Not loaded Distinct public accounts in the returned bid and ask samples.
Reference price Not loaded Two-sided funded midpoint preferred; AMM spot used as fallback.
JCS reference USD Not loaded Reference XRP price multiplied by CoinGecko’s XRP/USD value.
XRP/USD Not loaded External market reference; not an XRPL-native value.
XRP 24-hour change Not loaded External CoinGecko reference when available.

Funded JCS sell offers

Maker JCS XRP XRP/JCS
Load metrics to inspect the book.

Funded JCS buy offers

Maker JCS XRP XRP/JCS
Load metrics to inspect the book.
How these metrics are calculated and what they cannot prove
  • All XRPL requests specify or rely on validated-ledger data when the method supports it.
  • Order-book amounts use taker_gets_funded and taker_pays_funded when present, falling back to the full offer only when the offer is not partially funded.
  • Trust-line retrieval is paginated but capped to reduce load. A capped sample is labeled rather than represented as complete.
  • Wallet addresses are not verified real-world identities, and multiple addresses may be controlled by one party.
  • Price, spread, depth, pool value, holder count, and indicative network value can change before another person loads the page.
  • No metric proves faith, truth, legality, solvency, intent, ownership, future price, or future project success.

Living roadmap

The roadmap prioritizes ministry purpose, human safety, privacy, accessibility, technical reliability, and truthful disclosure rather than promotional milestones.

Updated as the project is tested
Live

Canonical JCS identity and public XRPL metadata

The domain, Web DID, security contact, issuer, currency, token metadata, and public source repository are independently inspectable.

Live

Prayer NFT and public testimony application

Sign the Ledger provides explicit Xaman-authorized prayer artifacts, testimony records, replies, and reactions.

Active

File-by-file modernization and security hardening

Identity, styles, documentation, discovery, legal pages, wallet flows, metrics, and mobile behavior are being reviewed in controlled commits.

Active

Plain-language transparency and accessibility

Improve readable disclosures, keyboard use, reduced-motion behavior, narrow-screen containment, language support, and privacy-conscious media loading.

Planned

JCS Fellowship account and Circle foundation

Add secure accounts, passkeys or wallet identity, invitation controls, blocking, reporting, moderation queues, appeals, and small-group permissions.

Planned

Private communication and recovery

Design encrypted messages, secure recovery, data minimization, retention controls, abuse reporting, and a clear separation between private content and public evidence.

Planned

Prayer Garden, Scripture Path, and Acts of Mercy

Build meaningful interactive experiences without pay-to-win, gambling, spiritual ranking, manipulative streaks, or crisis-content monetization.

Planned

Independent review and production operations

Introduce least-privilege services, backups, audit logs, rate limits, incident response, child-safety review, accessibility review, legal review, and independent security testing.

JCS ecosystem directory

Official JCS pages, public identity records, independent market interfaces, and related XRPL development work.

Official and independent links
JCS HomeFaith, Scripture, media, wallet, and JCS interaction portal Sign the LedgerPrayer NFT, testimony, reply, and reaction application Prayer & Integrity MapRead-oriented public XRPL visualization JCS MetricsEarlier standalone market-data surface scheduled for upgrade Privacy PolicyWallet, public-ledger, browser, NFT, and third-party disclosures Terms of ServiceRules and limitations for JCS website and application use SecurityResponsible vulnerability disclosure and project boundaries AI ManifestMachine-readable project and resource description Web DIDCanonical decentralized identity for the JCS domain XRPL TOMLIssuer, currency, token metadata, URLs, and security boundaries BithompIndependent issuer and ledger explorer XPMarketIndependent JCS market-data interface SologenicIndependent JCS/XRP DEX interface Public repositoryVersion history and publicly viewable source Official JCS account on XPublic project communication Related XRPL toolingXRBitcoinCash security, auditing, and ledger-analysis ecosystem

Important boundaries

The project’s religious mission does not remove technical, financial, privacy, legal, or human limitations.

Read before relying on the project