Jump to content

PunishmentOfLuxury

Bronze Member
  • Content Count

    993
  • Joined

  • Last visited

  • Days Won

    1

PunishmentOfLuxury last won the day on April 20 2017

PunishmentOfLuxury had the most liked content!

7 Followers

About PunishmentOfLuxury

  • Rank
    Advanced

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm sure I saw Wietse say on Twitter that this would be okay, but that it would make it easy to link one owner to several XRPL accounts, and possibly undesirable for that reason.
  2. But the MessageKey ETH-like address is the destination for the Spark airdrop, so it's not meaningless to the Flare network. And ETH addresses have both upper case and lower case characters, like this: 0xf92864ad4C4A3d3Ed4e6C28009A8c3da7768CA55. If you convert lower case to upper then it's a different address, isn't it? And the original address cannot be reconstructed from the MessageKey version because no algorithm can tell which letters were lower case. So how does the Spark get sent to the correct address for which you generated the key pair?
  3. One thing I'd like explained: why are we told to convert all lower case letters in the ETH address to upper case? Isn't that destroying information since 'A' is different from 'a' in base 58 (or whatever it is) crypto addressing? I can't just substitute capitals for lower case when I'm sending to an address on the Ethereum network, so how can it work for Flare? Won't the Spark airdrops be misdirected?
  4. Tool to see if your XRPL account is enabled: Flare airdrop checker Neither tested nor recommended by me, but no reason I can see to think it's not legit. Source code available.
  5. No more risk than signing any other kind of transaction on the XRPL.
  6. #!/bin/bash read -p "ETH address you want to convert to XRPL MessageKey? " string string=${string//0x} string=${string^^} echo "Done: 02000000000000000000000000${string}" A simple bash script I wrote to use instead of Wietse's online tool to convert an ETH address to the required format. Use offline in conjunction with Bithomp Tools to set your MessageKey.
  7. Re generating new key pairs: the latest MEW website and app will not reveal the private key after wallet creation. However you can download the vintage myetherwallet zip from Github , extract and run it offline. Just go into the dist directory and load index.html into your browser. You can save the address and private key by printing to a file within Firefox, for example.
  8. Now I'm totally confused. You said earlier: How can we generate a Flare key pair now when the Flare network doesn't exist yet? Spark will only exist on the Flare blockchain, not on the Ethereum blockchain, so the Spark tokens cannot be sent to an ETH address, surely? The fact that the address formats are the same is irrelevant, isn't it? EDIT: Or is it irrelevant that the key pair generation process is the same for both networks, since address collisions/duplications are simply staggeringly unlikely?
  9. So there's no point doing anything with MessageKey at the moment. We have to wait until the Flare network is up and running and create an account on it and put that Ethereum-like address into the MK field on our XRPL accounts. Right? And presumably that also means that the ETH tools for key pair generation cannot be used, such as those in the bitcointalk thread mentioned by @Flintstone.
  10. Very good guide. I would add that the transformation of the ETH address to the required format can be done with this tool from Wietse: https://flare.wietse.com/ Just ignore the bits about Xumm and Ledger if you're not using those. Now the final piece for me is how to generate new Ethereum addresses WITH access to the secret keys (MEW no longer gives the latter). Any simple, foolproof way?
  11. My XRPL family seeds (s............) are deeply buried. There's always a small risk involved in digging them up and displaying them on a computer screen.
  12. My airgapped PC never went online after the first installation and never will again. Updates aren't important if there's no attack vector and you have the functionality you need. Raspbian and Ubuntu come with Firefox pre-loaded IIRC. I download needed files such as Bithomp Tools, Ripplerm on a thoroughly virus-scanned online PC. Scan the files again. Scan the Kingston Data Traveler Vault Privacy USB stick (which requires a passphrase for access), put the files on that, then move them over to the airgapped PC. I admit the USB stick is a potential attack vector, but I'm happy I've minimsed
  13. I can't agree. A properly secured, airgapped PC can be every bit as safe as a Ledger. Physical access to my PC, even for years, won't get anyone one drop of my XRP. (And to be sure you won't lose your keys on the Ledger you have to secure the 24 word mnemonic for it, so you're pretty much back to square one.) Please see the threads that @Kakoyla and I co-operated on about how to create a PC cold wallet. Learn coding just for this? That's like saying if my car's wheel nuts are loose I should learn to forge steel and machine my own wheelbrace. I am happy to use third party tools from reputa
  14. In that case what would you recommend for offline transaction signing of this AccountSet/MessageKey on an airgapped PC? I don't think your tool will do that? QR code representation of the TX blob for submission via Xumm or Bithomp would be ideal.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.