Xferion
Xferion is a Discord bot. It posts public blockchain activity and public exchange activity to the blockchain activity channel on the XFER Discord server. It does not send direct messages. It does not keep personal data or message content beyond what it needs to stay running.
Web wallet
The wallet on this site is non-custodial. The 12 words are created in the browser. A password you choose encrypts them in this browser. The words are used in this browser to sign. They are not sent to the relay. A different browser does not have them until you restore from the words you wrote down.
The relay does not hold the wallet. To show a balance, the browser sends addresses. The relay reads the public chain for those addresses and sends back balances, assets, and raw transaction hex. When you send, the browser signs the transaction here and sends that signed raw transaction hex to the relay, which broadcasts it. The relay does not receive the 12 words or a private key.
This browser also keeps a few notes for the site itself, such as the theme and the record that you accepted the Terms of Use. Those stay on this device.
Sign in with X
Sign in with X is optional. The site sends you to X to approve access. That request asks for users.read and tweet.read. X requires tweet.read for the users/me lookup. After you approve, the relay reads your X user id, username, and verification status from X. It does not fetch your posts. The access token is not kept.
A cookie in your browser stores the user id, username, and verification status for 30 days, or until you sign out. The relay rejects the cookie after those 30 days, including a cookie that never had an expiry. The relay also writes sign-in and claim cooldown times. Those records can include a random cookie id, the IP address, the X user id, and the handle, and entries older than 7 days are removed.
If you claim a name, the chain stores a public record that ties that X handle to an address you choose.
Pinning media
You can attach a JSON file, a picture, or a video to a token. The browser uploads that file to the relay. The relay sends it to Pinata, which pins it on the public IPFS network. The Pinata credential stays on the relay and is not sent to the browser.
Before the upload, the vault signs a short challenge so the relay knows which address is pinning. The 12 words are not part of that upload. The relay counts pins per address for the day: 10 with no extra fee, then 5 XFER each. That count is kept in memory. A paid pin also stores the fee transaction id so it cannot be reused. The file is public. This site and the explorer load it from a public gateway, and the content id can be written on the chain with the asset. A listed file can also be pinned again from that content id.
What the site shows
This website, the web wallet, and explorer.xferchain.net show public chain data: blocks, transactions, addresses, and assets. A picture or file linked from an asset is loaded from a public gateway. The site can also show a public exchange price for XFER.
The web server keeps an access log. That log includes the visitor IP address. It is used to run the site, including rate limits on chain reads.
Contact
Questions about this page can be emailed to support@xferchain.net. Any review is best-effort and without obligation. Emailing that address does not create a support desk or a duty to respond.
This page may be updated by posting a new version here. The date at the top changes when that happens.