Jump to content

PunishmentOfLuxury

Bronze Member
  • Content Count

    993
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    PunishmentOfLuxury got a reaction from JASCoder in Flare networks - Spark token to XRP holders   
    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. Thanks
    PunishmentOfLuxury reacted to JASCoder in Flare networks - Spark token to XRP holders   
    You will notice the string of characters in your example contain no letter above the "F" - the exception is the base indicator of the leading 0x (zero ex).
    Hexadecimal is represented by the alphanumeric digits 0-F, and is case insensitive.
    Any code parser will pre-filter any hex string to a uniform case (traditionally upper) prior to use in any numeric operation. 
    I hope this is helpful.
    Cheers.
    Ref: https://www.includehelp.com/c/working-with-hexadecimal-values-in-c-programming-language.aspx 
  3. Thanks
    PunishmentOfLuxury got a reaction from FineSir in Flare networks - Spark token to XRP holders   
    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.
  4. Thanks
    PunishmentOfLuxury reacted to SimpleXRPTools in Flare networks - Spark token to XRP holders   
    The Ethereum addresses aren't case sensitive but the capital letters serve as a checksum. See here: https://coincodex.com/article/2078/ethereum-address-checksum-explained/
  5. Thanks
    PunishmentOfLuxury reacted to xrpthestandard in Flare networks - Spark token to XRP holders   
    No, Ethereum addresses are in HEX so they are not case sensitive.
  6. Like
    PunishmentOfLuxury reacted to jetbrzzz in Flare networks - Spark token to XRP holders   
    I remember trying to submit a Flare address to the messagekey but in all lower case (just because) and it wouldn't take so I think it's an XRPL thing, all upper-cased hexadecimal. Also pretty sure like you said the 02 + 24 zeros is a parsing thing; I was skimming over Wieste's code (I think) that scans the XRPL for valid Flare addresses and it searches messagekeys for matches to "0200", something to that effect.
    https://xrpl.org/accountset.html
    It's formatted the same way in the example AccountSet.  I think it's purely formatting/parsing related. Flare Networks can/could easily write a script to (lowercase everything + remove all the zeros + re-add the 0x prefix) for all addresses if that is what is required for the Ethereum Virtual Machine, no biggie. I have those kinds of bash scripts myself, they're a 2 or 3 liner at most.  Something akin to:
    [while read addr;
    do (all-the-conversion-things);
    done] < file-list-of-all-flare-addresses-from-XRPL
  7. Like
    PunishmentOfLuxury reacted to KarmaCoverage in Flare networks - Spark token to XRP holders   
    Maybe it is for easier parsing of Ledger data, idk. Remember the ETH address is only a MessageID on the XRPL, so it is rather meaningless.
    More digits should increase cryptography, while (as you point out) reducing potential character could would reduce it.
    I have a feeling the answer is a combo. Dosent really matter b/c it's just a MessageID + sets the stage for long cryptography keys.
  8. Like
    PunishmentOfLuxury got a reaction from KarmaCoverage in Flare networks - Spark token to XRP holders   
    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?
  9. Thanks
    PunishmentOfLuxury reacted to Dogowner5 in Flare networks - Spark token to XRP holders   
    Because so many people seem confused about this whole claim process I am going to write a short explanation of what happens and why.  It’s not a how to...  others are doing that.  It’s a ‘what happens and why’.  I won’t explain why all this is so good for XRP... that’s another topic.  Let me know if any of this is badly worded or needs more explanation.
     

    Flare want to do Smart Contracts 2.0.   Etherium is slow and expensive and has some potential governance/security issues even as it changes from Proof of Work to Proof of Stake.  Also, POS is an inefficient use of capital.
    So they are taking the Etherium smart contract engine holus bolus and putting it on a newly created consensus network.  This would enable Etherium smart contract users to simply copy paste their contracts over to Flare so they are faster and cheaper than when they ran on Etherium.
    Because the smart contracts use Etherium type addresses, so too must the Flare network.  Flare want to interact with all networks eventually,  but the one they are starting with is the XRPLedger.  So their network is XRPL aware.  It can read the XRP Ledger and monitor it.
    Any new blockchain needs a distribution strategy for its native token (in this case: Spark).  It’s not a trivial thing to do.  It’s been done badly many times.
    Flare decided to distribute Spark to any interested XRP holders (except for Ripple and Ripple Founders).
    So how to do that?

    They let XRP holders express interest by advising their desired receiving address.
    They need the interested XRP account holder to nominate a Flare address to send the Spark to from the Flare genesis account.  They could do that in some convoluted way,  but they wanted the distribution to be handled without any intervention by a smart contract running on the Flare network that will run for six months after the initial start on snapshot day.

    It needs to know what Flare address to send the Spark to.  So they have asked the XRP account holder to set a (mostly unused) field in their XRP account with the desired Flare address.  This does four things.  First it lets the contract know that this person wants Spark.  Because it can read the XRP balance it knows to allocate a corresponding amount of Spark.  Thirdly it proves the owner of that XRP is the one giving the receiving address (only the owner can make account changes).   Lastly it tells the contract where on the Flare network to send the Spark.
    So after this is done they have two separate blockchains: Flare and XRPL.  Some (maybe most?) XRP holders will have tokens on both.  The XRPL is unaffected. 
    They set a “snapshot” date of 12/12/2020.  Any XRP account that sets that MessageKeyField with a valid Flare address will receive Spark to that Flare address.  For the next six months after the snapshot,  any XRP account that sets the address (and hasn’t previously) will be allocated Spark.  The smart contract will be watching every ledger close over that six months and will send Spark when it sees a newly and correctly set MessageKeyField.
    After the six month grace period expires any remaining unallocated Spark will be burned.
    So I hope that makes thing clearer for any wondering about it.
     
    Some key points:
    Setting the field wont affect your XRP.  That field can be cleared later if you don’t like it being there. If you set it before snapshot you will get Spark on day 1 If you don’t have it set at snapshot, but set it In the six months after, then you will receive the Spark immediately the contract sees the ‘set’ transaction on the XRPL  If you self manage your XRP you need to do this address set yourself If you are on a participating exchange then they will claim them for you and advise you how to access them If you are on a nonparticipating exchange you won’t get any Spark (but they might claim and keep them)  
    If you do this yourself you should make absolutely certain that you have control of that Etherium/Flare address.  It’s not enough to just have the address...  you must have the related private key also.  
    There is no guarantee that Spark will be worth anything While you have that field set it allows others to know what address your Spark started to live at.  No biggee but some (me) will remove it as soon as it’s been allocated just on general privacy principles.   EDIT:  Of course, anyone interested can always traverse the ledger to find your set tran and therefore you initial Spark address.  Again, no biggee.  
    Hope this has been helpful.     
     
     
     
  10. Thanks
    PunishmentOfLuxury got a reaction from jetbrzzz in Flare networks - Spark token to XRP holders   
    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.
  11. Like
    PunishmentOfLuxury got a reaction from Warbler in Flare networks - Spark token to XRP holders   
    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 reputable people like @Warbler offline on my airgapped PC. I already managed a trial run of creating the MessageKey transaction on test-net using Ripplerm wallet. It's not too difficult, but that wallet does lack a QR function.
  12. Like
    PunishmentOfLuxury got a reaction from Flintstone in Flare networks - Spark token to XRP holders   
    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.
  13. Thanks
    PunishmentOfLuxury got a reaction from Global in Flare networks - Spark token to XRP holders   
    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.
  14. Thanks
    PunishmentOfLuxury got a reaction from Zerpiet in Flare networks - Spark token to XRP holders   
    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.
  15. Like
    PunishmentOfLuxury got a reaction from KarmaCoverage in Flare networks - Spark token to XRP holders   
    No more risk than signing any other kind of transaction on the XRPL.
  16. Like
    PunishmentOfLuxury got a reaction from Flintstone in Flare networks - Spark token to XRP holders   
    #!/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.
  17. Like
    PunishmentOfLuxury got a reaction from jetbrzzz in Flare networks - Spark token to XRP holders   
    #!/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.
  18. Like
    PunishmentOfLuxury got a reaction from RobertHarpool in Flare networks - Spark token to XRP holders   
    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.
  19. Like
    PunishmentOfLuxury reacted to Dogowner5 in Flare networks - Spark token to XRP holders   
    So I have up to 11th June 2021 to set the message key.  I’ll get right on that.   
  20. Thanks
    PunishmentOfLuxury got a reaction from ZeeperCreeper in Flare networks - Spark token to XRP holders   
    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.
  21. Thanks
    PunishmentOfLuxury got a reaction from Zerpiet in Flare networks - Spark token to XRP holders   
    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.
  22. Thanks
    PunishmentOfLuxury reacted to jetbrzzz in Flare networks - Spark token to XRP holders   
    The Flare Network is using Ethereum-compatible addresses for it's address format (I don't know why, but that's what's in the the release notes).  Yes, they're completely different blockchains, but like I said, they're leveraging some part of the Ethereum Virtual Machine in the Flare Network so maybe they have to have Flare Network addresses formatted in an Ethereum-compatible way for some reason.
    I don't think it matters, it seems like they built the network to accept Ethereum-compatible addresses so even if you used an existing Ethereum wallet for the Flare Network, I imagine the Flare Network would only acknowledge activity on the Flare Network ledger regarding that account.  Flare Network would have no knowledge of your Ethereum history on that address since it is a completely separate ledger.
    I wouldn't personally reuse an ETH wallet like that and they mention in the notes why you might not want to set it up like that.
    I think the key pair generation process is irrelevant like you said, in the release notes they specifically say to get an Ethereum-compatible address.
    https://flare.ghost.io/claiming-spark-faq/
    Straight from the notes.
  23. Like
    PunishmentOfLuxury reacted to Flintstone in Flare networks - Spark token to XRP holders   
    @vrippled The simplest method is to download https://github.com/Bithomp/bithomp-tools 
    Extract the download file.
    Then open the index.html file in a browser in private mode. That will load the wallet.
    The trouble is, you have to now enter your secret key s************. You can disconnect from the internet at this point, but do you know if there is any malicious software on your computer? This is why an ‘airgapped’ computer is recommended - A computer that never sees an internet connection.
    For an airgapped computer, transfer the downloaded file to USB stick and then to the airgapped computer and extract there.
    Once your secret key is entered into the wallet, click on the ‘settings‘ button and then select the ‘message key’ button.
    You need to now find out the sequence and fee values. Use a QR reader or camera app to scan the QR to find out these values.
    Now follow these instructions given by Wietse:
    Take a ETH-compatible public account address you own the private key (or secret, like mnemonic, seed, ...) of, eg. 0x415f8315c9948Ad91e2Cce5b8583A36dA431fb61
    Strip the first two characters, and turn the string to upper case characters: 415F8315...A431FB61
    Prepend 02 and 24 zeroes: 020000...000415F8315...A431FB61
    Store this value in the MessageKey field on your XRP ledger account (on ledger) using an AccountSet transaction

    Once you submit the transaction, it will generate a QR code.
    Scan the code with your phone using a QR reader. Some phones camera app have a built in reader or you can download one from your app/play store.
    This will enable you to copy the signed transaction data which you can then submit to the XRPLedger via Bithomp Explorer.
    That should be it done. MyEtherWallet is a popular ETH wallet if you need one.
  24. Thanks
    PunishmentOfLuxury got a reaction from jetbrzzz in Flare networks - Spark token to XRP holders   
    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.
  25. Like
    PunishmentOfLuxury reacted to Flintstone in Flare networks - Spark token to XRP holders   
    That’s that done. Here’s an example on Bithomp Tools.

     
    Transaction states on Bithomp Explorer ‘Flare address added’
×
×
  • 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.