palskia.xyz

Your wallet just found a frequency.

A wallet-native private communication network — encrypted messages, permissioned contact, and settlement inside the same thread. This page is the whole position: how it works, what runs today, and what's still ahead.

Encrypted end to end Relay and client live No email, no phone

At a glance

Six numbers worth knowing before you read the rest. Each one comes straight from the chain config or the relay's own behavior — update them in src/data/site.ts as your deployment firms up.

Encryption nacl.box x25519 · xsalsa20
Network Set your chain the launch network
Chain ID 0 0x0
Block time ~100 ms sub-second finality
Gas token ETH 18 decimals
Settlement TBD unconfirmed

Value found its rails.
Everything around it did not.

  1. 01

    A wallet can move value and say nothing else

    Every conversation around a transfer happens off to the side — a group chat, a DM, an email thread — where the other party is a screen name, the agreement is a screenshot, and the app holding the conversation isn't the one holding the funds.

  2. 02

    The address is already a valid identity

    It's verified, portable, and carries a keypair on its own. Give it an inbox and it needs no phone number and no signup: prove the address, derive a messaging key, publish the public half.

  3. 03

    Attention is the scarce, priceable thing

    A stranger can't just message you — they can signal, and a signal can carry a refundable bond. Accepted threads carry payment requests that settle on-chain. That's the surface worth pricing: access, not content.

How it works

Four moves. None of them asks for an email.

01

Connect

Connect an EVM wallet and sign in. Two signatures: one proves you hold the address, the other derives the messaging keypair.

No password, no email, no phone number
02

Claim a handle

Publish a name and a public key against your address. Anyone can resolve the handle to the key — nobody can open a message without it.

Directory record, no gas, no transaction
03

Signal

You can't be messaged without permission. A stranger sends a signal; you accept, decline, or block it. Nothing reaches your inbox before you choose.

A blocked signal is silent — it goes nowhere
04

Talk, then settle

Messages are sealed to your published key with a fresh one-time keypair each time. A payment request can live in the thread and settle on-chain.

Amounts carried as integer minor units

Token & supply

The distribution and unlock schedule, pulled from the same file that renders this page — the two can't drift apart.

PALSKIA
Total supply 1,000,000,000
Standard ERC-20
Float at listing 6.0%
Contract address Set after deployment
Relay incentives
32%
Set vesting schedule
Ecosystem & grants
18%
Set vesting schedule
Core contributors
17%
Set vesting schedule
Early backers
15%
Set vesting schedule
Treasury
12%
Released by governance vote
Public distribution
6%
Unlocked at listing

What's built

3 of 8 capabilities run end to end today. The rest are named here rather than implied by silence.

Wallet sign-in Working
Nonce, signature, session token. One signature proves the address, one derives the messaging key.
Encrypted messaging Working
Sealed against the recipient's published key with a fresh one-time keypair per message. The relay is built to never hold plaintext.
Signal & permission layer Working
Accept, decline, block. A blocked signal is a dead end by design, not by convention.
Payment requests Partial
Requests and receipts run end to end. Nothing yet reads the chain to independently confirm a settlement hash.
Anti-spam bonds Partial
A bond amount can travel with a signal. No contract locks or returns it yet.
Groups & file sharing Planned
Conversations are one-to-one for now. Group keying and file transport are phase-two work.
Multi-device history Planned
Keys re-derive from a signature, but history doesn't travel with them yet.
Relay decentralization Planned
A single relay today. Fine for a first build, not yet for a network.

Order of work

No dates, because there are none to give. What's fixed is the order — nothing in a later phase starts before the one above it is done.

  1. Phase 0 In hand

    The protocol, working

    • Relay, encryption, and the signal layer running end to end
    • This page, published and kept honest against the code
    • A launch chain wired in
  2. Phase 1 Next

    Make it safe to rely on

    • Independent cryptographic and security review
    • Rate limiting, abuse handling, key rotation
    • A worker that verifies settlement against the chain itself
  3. Phase 2 Later

    Make it a network

    • Multiple relays, so delivery survives any single one
    • Groups, file transport, multi-device history
    • Bonds held by a contract instead of a database row
  4. Phase 3 Later

    Hand it over

    • Governance over treasury and emission
    • Contract audits published in full
    • Legal review before any wider distribution

Read this part twice

The things a reader is most likely to get wrong.

  1. Encryption is not anonymity

    Who talks to whom, when, and how often is visible to the relay. So are handles, public keys, and the addresses behind them.

  2. Payment metadata is in the clear

    Amount and participants are stored unencrypted so receipts can render, and settlement lands on a public chain.

  3. Nothing here is audited yet

    No security review, no cryptographic review, no contract audit. Treat this as a working prototype, not a place to hold funds you can't afford to lose.

  4. Palskia will never message you first

    It will never ask for a seed phrase or a private key. Verify every link against this domain — an unsolicited offer is a scam.

Nothing on this page is an offer to sell or a solicitation to buy any asset. Verify every link against palskia.xyz directly.

Your wallet
has a channel now.