Christ centered
Every feature should direct attention toward Jesus Christ rather than speculation, personalities or technological novelty.
Christ centered · non-custodial · privacy conscious · verifiable
Technology as a vessel.Faith and human dignity first.
Jesus Christ Saves Token is a Christ-centered XRP Ledger application ecosystem built to make Scripture, prayer, testimony, service, fellowship and transparent public evidence easier to encounter and preserve—without making token ownership, wallet balances or blockchain participation a measure of spiritual worth.
No pay-to-prayNo token-weighted theologyNo custody of wallet secretsPublic evidence ≠ spiritual authority
What the project is trying to build
The goal is not to make a blockchain substitute for Christianity. The goal is to build durable, transparent and privacy-conscious tools that can carry Christian content, prayer evidence, fellowship and service across platforms while keeping user agency intact.
Safety and human dignity
Core prayer, Scripture and safety resources should not depend on wealth, token ownership or public self-identification.
Non-custodial participation
Users review and authorize wallet actions through Xaman. JCS pages should never request a seed phrase, recovery phrase or private key.
Transparent infrastructure
Issuer identity, public transactions, market structure and ledger evidence should remain independently inspectable.
Voluntary witness
Prayer, testimony, NFT, trading and public social actions require deliberate user choice; passive browsing should remain available.
Stewardship over hype
JCS is not a promise of profit. Utility, clarity, safety, responsible disclosure and service take priority over promotional claims.
“And the Word became code, and the code dwelt among us.”Creative JCS project language. It is not a quotation from Scripture and is not a replacement for Scripture, prayer, church, pastoral care or faith in Jesus Christ.
Current JCS application ecosystem
Each surface has a different purpose and risk boundary. The project intentionally separates read-only evidence, public religious content, local/private processing and ledger-changing actions.
Main Portal
Scripture, sacred media, fellowship tools and a non-custodial JCS/XRP exchange workflow in one portal, with sacred and financial actions deliberately separated.
Open portalSign the Ledger
Composes prayer/testimony records, mints user-controlled prayer NFTs and publishes validated public registry evidence through deliberate Xaman approvals.
Open Sign the LedgerPrayer Map
Shows threshold-qualified broad prayer groups beside independently labeled Christian-pressure, religious-freedom and media context without inferring a participant's real-world location.
Open Prayer MapPrivate Capsule
Browser-local AES-GCM encrypted transport plus separate recovery-key material. An optional neutral NFT can anchor only a fingerprint—not plaintext, routes, exact locations or the key.
Open capsule toolsNetwork Observatory
Measures public JCS communications, validated ledger health, trust-line and liquidity conditions, and privacy restraints without creating a composite spiritual-impact score.
Open ObservatoryAccount Readiness
Uses Xaman account-control authorization or public address lookup to inspect a pinned validated-ledger snapshot, JCS relationship, NFTs, flags and protocol objects without creating a signing payload.
Open Account ReadinessMachine-readable identity
Web DID, XRPL TOML, AI manifest, robots policy, sitemap and security.txt provide stable identity, discovery and responsible-disclosure surfaces.
Open AI manifestPolicy & licensing
Dedicated legal, privacy, security and proprietary-license documents define the project boundaries more authoritatively than this summary route.
Review boundariesIndependent verification
Bithomp, XRPSCAN, XPMarket, Sologenic and public XRPL servers may be used for independent context. They are separate services and are not controlled by JCS.
Verify issuerEthical access principles
The project direction rejects financial or engagement mechanisms that would turn spiritual participation into a paywall, popularity contest or urgency loop.
No pay-to-pray
Basic prayer participation, Scripture access and safety resources should not require a token purchase.
No pay-to-be-heard
Money or token balances should not buy spiritual priority, crisis priority or doctrinal authority.
No token-weighted theology
Wallet balances do not determine truth, faithfulness, salvation, religious leadership or personal dignity.
No outrage engine
The long-term social direction should favor finite, meaningful interactions over compulsive scrolling, artificial urgency and engagement extraction.
Optional utility stays optional
Future token utility may support evidence, customization, creator tools or reusable access, but not basic spiritual participation or emergency resources.
Quiet and Sabbath design
The platform should be able to tell people that they have done enough for the day and help them leave the screen.
Safety for people whose faith may carry risk
Public blockchain transparency can conflict with personal safety. JCS therefore treats location restraint, silent access and user-controlled disclosure as core product requirements rather than optional polish.
Do not infer physical location
Wallets, nodes, relays, browsers, Xaman devices, transaction routes, prayer text and public keys must not be interpreted as a person's physical location. Prayer Map labels describe a prayer focus, not where the signer lives.
No public extraction routes
The public map must not publish escape routes, safe-house locations, movement plans or individual travel paths. Thresholded lines represent aggregate support relationships only.
Private Capsule is local-first
Private Capsule can encrypt a limited message locally, but it is not a guarantee against malware, hostile extensions, device compromise, physical coercion or mistakes in key handling.
Public XRPL records persist
A wallet address, transaction, memo, NFT or public registry entry can remain visible even if the website later changes. JCS cannot privately erase a validated XRPL transaction.
High-risk boundary: JCS is not an evacuation service, clandestine-operations platform, emergency dispatcher or replacement for qualified high-risk digital-security assistance. People in immediate danger should avoid publishing exact locations, routes, safe houses, identity documents or operational plans through a public blockchain workflow.
Where the project is headed
The current deployment is primarily a static client-side foundation. A durable Christian social network requires separate backend and trust infrastructure. These are design goals, not guaranteed features or delivery dates.
Identity & sessionsPasskeys, Xaman and DID-based identity options, recovery and carefully scoped account/session services.
Faith CirclesPermissioned small-group prayer, study and service spaces with clear moderation and membership boundaries.
Private messagingDedicated message encryption, key recovery and delivery infrastructure separated from the public ledger and static frontend.
Moderation & safetyBlocking, reporting, appeals, abuse prevention, rate limiting, anti-spam, child-safety review and incident-response workflows.
Acts of MercyPrivacy-conscious ways to request or offer practical assistance while revealing only the minimum necessary information.
Scripture PathReading journeys, memory exercises, reflection prompts and collaborative study milestones without gambling or pay-to-win mechanics.
DurabilityBackups, audit logs, account recovery, accessible translations, cross-device continuity, media storage and content-safety controls.
Least privilegePrivileged services should be introduced as separate components; secrets and sensitive authorization logic should not be pushed into the static GitHub Pages frontend.
Legal, application and reliance boundaries
This section summarizes important project-wide disclosures. It is intentionally conservative. The current Terms, Privacy Policy, Security page and repository LICENSE control their respective subjects and should be read directly.
| Area | What the project can do | What it does not establish or guarantee |
|---|---|---|
| Religious mission | Describe a Christ-centered religious, educational and outreach purpose. | This page does not independently create or prove church status, nonprofit status, public-charity status, tax exemption or recognition under Internal Revenue Code Section 501(c)(3). |
| Wallet authorization | Xaman can return a public XRPL account selected or controlled for a session. | Session account control is not government identity, legal identity, moral character, pastoral authority or truth of an off-ledger claim. |
| XRPL transactions | Interactive pages can prepare transaction requests for independent Xaman review and later verify validated results. | No signature, submission or UI success message guarantees a desired economic result. Validated ledger records can be irreversible and public. |
| JCS token / markets | Provide token identity, liquidity, market and ledger context and non-custodial transaction tools. | No promise of profit, liquidity, price, market capitalization, availability, adoption, appreciation, suitability or investment return. |
| NFTs & hashes | Timestamp or bind a technical fingerprint and create user-controlled digital artifacts. | An NFT, hash or timestamp does not automatically prove authorship, truth, legal ownership, copyright, authenticity, regulatory compliance, pastoral authority or legal effect. |
| Prayer / testimony | Allow voluntary public religious records and local-first private tools. | Blockchain activity does not measure salvation, prayer effectiveness, doctrinal truth, sincerity, human worth or divine response. |
| Prayer Map | Display threshold-qualified prayer-focus groups beside separately sourced context. | Map activity does not prove where a signer lives, that an incident occurred at a marker, or that prayer caused a change in real-world conditions. |
| Private Capsule | Encrypt selected content locally and optionally anchor a neutral public fingerprint. | Not zero-risk, not zero-knowledge against every provider or endpoint, not safe against a compromised device, and not an emergency or covert-operations service. |
| Account Readiness | Inspect a validated public ledger snapshot and JCS-specific account relationship. | No security certification, solvency opinion, identity certification, financial suitability determination or prediction of future behavior. |
| Metrics / AI / automation | Calculate observed and derived indicators and expose machine-readable project descriptions. | Derived values, automated classifications and AI interpretations may be incomplete, stale or wrong and must not be promoted into unsupported factual, legal, financial or spiritual claims. |
| Third parties | Link or interoperate with XRPL, Xaman, GitHub, explorers, exchanges, market-data, media, mapping and research services. | No endorsement, partnership, custody, sponsorship, certification, shared control, availability guarantee or adoption of those providers' terms by JCS. |
| Future roadmap | Describe intended design directions and experiments. | No roadmap item is a contractual promise, warranty, delivery date, funding commitment or guarantee that the feature will ship. |
No composite impact score: prayer counts, wallet participation, market activity, map cohorts, response rates and ledger metrics remain separate observations. JCS does not combine them into a score of faith, spiritual effect, human worth, safety or project success.
No professional-advice boundary: project content and software are informational and experimental. They are not financial, investment, legal, tax, accounting, medical, mental-health, emergency-response, pastoral or cybersecurity advice. Obtain qualified professional advice where appropriate.
Use at your own risk: software defects, browser behavior, third-party outages, public-ledger immutability, phishing, malware, market volatility, liquidity failure, fees, slippage, user error, regulatory change and other events can cause loss, exposure or unexpected results. Review every Xaman request and decline anything that does not match your intent.
Licensing and intellectual-property boundary
Public source visibility is not the same thing as open-source permission. This route summarizes the current repository LICENSE; it does not replace or amend it.
All rights reserved
Covered JCS material is proprietary. It is not automatically licensed as open source, free software, Creative Commons, public domain or a general noncommercial license merely because the repository can be viewed.
No automatic reuse grant
Absent permission or an applicable legal right, public access does not grant permission to copy, modify, redistribute, deploy, white-label, build derivative works, or use covered material for datasets or AI/model training.
Narrow watchdog exception
The LICENSE contains a specifically defined Qualified Federal Watchdog exception for authorized federal oversight purposes, subject to scope, duration and safeguards. It is not a general research or public-interest license.
Third-party material excluded
JCS ownership claims do not override third-party copyrights, public-domain status, platform rights, open standards, public XRPL records or other rights that belong to someone else.
Statutory rights preserved
The LICENSE preserves non-waivable legal rights, fair use where applicable, compulsory process and other rights independently supplied by law.
No implied affiliation
Use of JCS names, logos or code does not create endorsement, certification, sponsorship, partnership, regulatory approval, wallet authority or the right to act on behalf of JCS.
License-summary boundary: the complete repository LICENSE controls licensing rights and restrictions. This webpage is a convenience summary and is not a legal opinion or a court determination that any clause is enforceable.
Authoritative trust, policy and machine-readable records
Use the source appropriate to the question. Mission language should not override legal terms; UI summaries should not override validated ledger facts.
Authority order: use
about-jcs.html for the living mission and roadmap; Terms for contractual terms; Privacy for privacy disclosures; Security and security.txt for security; the repository LICENSE for reuse rights; and validated XRP Ledger data for ledger facts.Machine-readable project charter
Download a compact JSON description of the compatibility route, project identity, current surfaces, ethical-access rules, roadmap boundaries, license posture and source hierarchy.