Just like email addresses, a PayID can be issued to you by a provider. One PayID can contain multiple destinations (multiple rails), so one PayID can contain eg. your XRPL address, a bank account, a BTC address, etc.
To the educated eye, the commit history for the XUMM App & Backend mentioned PayID a few times already, in the past months ;) Hidden in plain sight.
So: open XUMM, tap Send, enter a random amount, and instead of entering the destination XRPL account address, try:
wietse$xumm.me
If you're a developer, own your own domain and know how to run a JS package: here's a simple static (TOML file) based PayID server: github.com/WietseWind/Pay…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Dear Xumm users in our homeland, The Netherlands 🇳🇱
The wait is over. You can now use On-ramp services: send EUR from your bank account to XRP in your XRP Ledger account.
Off-ramp will be added later this week.
Tap your Xumm "Home button" and On/Off-ramp will be listed.
🧵»»
🤔 How does this work?
You onboard once, we do the required KYC & Proof of Address. You can then open the On/Off-ramp xApp any time.
We give you a deposit description which you can use to send from your IBAN to our IBAN. Within minutes you'll have the XRP in your XRPL account.
🤔 What are the per transaction fees?
When turning your EUR into XRP and vice versa, we get you the best spot rates possible through our liquidity providers. We're talking *good* prices. Decent exchange prices, not those awful "buy crypto quick and easy" with 3+% markup prices.
As far as I know it's still not certain how the SOL attack happened. There are a couple of theories, the two most shared/speculated:
- Faulty crypto (signing) implementation
- Generated keys compromised (sent in plain text over the wire after generation)
While it's never 100% possible to say a wallet is not at risk (not even for hardware wallets) of any security issues, I feel it's safe to say that neither one of the speculated issues apply to Xumm.
We feel we are doing a better (more transparent) job than the wallets involved.
The crypto parts (and many other relevant components) of Xumm have been audited. The audit is still ongoing. There are some interesting findings, things we can improve. But overall no high risk remote exploitable, nor mass exploitable things found.
@TheHodlerX As far as I know it's still not certain how the SOL attack happened. There are a couple of theories, the two most shared/speculated:
- Faulty crypto (signing) implementation
- Generated keys compromised (sent in plain text over the wire after generation)
@TheHodlerX While it's never 100% possible to say a wallet is not at risk (not even for hardware wallets) of any security issues, I feel it's safe to say that neither one of the speculated issues apply to Xumm.
We feel we are doing a better (more transparent) job than the wallets involved.
@TheHodlerX The crypto parts (and many other relevant components) of Xumm have been audited. The audit is still ongoing. There are some interesting findings, things we can improve. But overall no high risk remote exploitable, nor mass exploitable things found. support.xumm.app/hc/en-us/artic…
Most common attack vector used to scam crypto users? Tricking the users into entering their secret key, or sniffing it when a service asks for the secret. *NEVER* share your secret.
Did you know if you use @XummWallet@Tangem cards, this type of scam/attack won't work on you?
With the secret generated & stored inside a chip inside the card, you won't even have a secret to accidentally share.
Not having the secret is not a recovery problem if you configure a second "back up" card. Takes just a few minutes. This his why we sell min. two cards.
And what about the most common cause of users losing access to their funds? Lost secret keys. When you lost your secret key and still have access to your phone, you can "rekey" (configure a new secret). What if you find out you lost your secret key after you got a new phone?
I'm getting a lot of questions about XRPL nodes, what they are, why they exist, what their specs are, etc. Here's what I replied in the past few days, hoping that it'll help more people.
There isn't one type of node. There are full history nodes, non full history nodes, validating nodes, etc. They run the same software, they are connected to the XRP Ledger, their config, use and hardware requirements are simply different.
Most questions I receive are actually answered by the XRPL.org documentation website. Lots of good and useful content here: xrpl.org/manage-the-rip….
Don't think you can run and maintain a node after skipping all that content. I can't offer you a shortcut.