 Show Posts
|
|
Pages: [1]
|
|
Consider Abra or Coins.ph
Some are expensive percentage over spot but it's probably OK unless you're doing large amounts.
|
|
|
|
|
Flat fee of $8.20 per transaction? Not a percentage?
|
|
|
|
Hello all. I'd like to integrate payment processing into a website and accept stablecoins (USDT, TUSD, DAI, PAXOS, etc) in a non-custodial way. It makes sense since there is no price slippage. Since ethereum based tokens are not HD wallets, there is no master public key to generate one-time-use addresses. I would want each customer to have a different payment address. Yes there are some merchant processors that accept all cryptos but they are charging 0.5%-1% and there is additional price slippage in the coin conversions. I am looking for something very similar to https://pay.bleumi.com but they are a custodial service. Any thoughts? It seems like a very obvious way to start accepting payments on a website. THANKS |
|
|
|
|
Did you get this figured out? Do you have access to your coins now?
|
|
|
|
|
Please post some more details to explain what you are working on. Tx fees are not set by a private key.
|
|
|
|
You could've just made a regular seed with electrum and use a BIP39/BIP44 derivation path though?
No, he couldn't. That's the whole point of this thread. Electrum seed mnemonics are NOT BIP39 compatible. If you try and put an Electrum seed menmonic into a BIP39 wallet, it will tell you that it is invalid and/or that the checksum has failed. The algorithm for creating the mnemonic from the same "seed" (ie. the big random number) is different... so even if you start with the same "seed", Electrum will generate a different mnemonic to a BIP39 wallet. For long term storage it's maybe a good idea to use a BIP39 compatible seed & also archive a copy of electrum software. |
|
|
|
|
Correct---I am not looking to use a 3rd party or give anyone else control over my keys. That's not what I'm talking about.
I tested sweeping paper wallets and hardware wallets and it just isn't supported with legacy addresses, nor is development planned. I appreciate the straightforward answer and it makes sense that future development would be toward native segwit wallets.
I now just need to learn if cold storage with native segwit (bc1 address) has any downside. I don't understand it as well, can't seem to get block explorers to work, and likely wouldn't receive future forks. I just need to learn more.
|
|
|
|
Ok, I answered my own question as I am stubborn and won't give up on this. This is a known issue ( https://github.com/spesmilo/electrum/issues/3302) So basically if using legacy addresses, no development is planned, but using native segwit, offline signing WORKS.  SomberNight commented on Apr 6 •
(updated: 2018-05-10)
Recap:
Trezor:
legacy does not work, no plan to implement support
✔segwit works
KeepKey:
legacy does not work, no plan to implement support
segwit: keepkey itself does not support segwit
Ledger:
legacy does not work, no plan to implement support
✔segwit works
Digital Bitbox:
✔legacy works (because dbb does not want previous transactions)
✔segwit works
|
|
|
|
|
Edit, I am using multisig when I received the error.
I created a test single signature wallet, and offline signing worked just fine....hmmm.
Any advice how to do multisig in an offline, cold storage environment?
|
|
|
|
I am on the latest client 3.2.2 and following the cold storage instructions here: http://docs.electrum.org/en/latest/coldstorage.html**The only difference is that when creating the transaction in the watch-only wallet, the "save" button is greyed out and now there is an "export" button. It creates unsigned.txn When I load unsigned.txn in the offline, air gapped computer (also running the same client version), and click "sign" it gives me the following error: Error: Server did not answer Can Electrum no longer sign transactions offline? Or am I doing something wrong? THANKS |
|
|
|
Announcement: as the 3rd party treasurer of b3 superblock I resign effectively immediately. This is just to inform some history and the reasons why. I was already banned in their discord, FYI. www.myfrogger.com is the announcement. |
|
|
|
|
Thank you for the update dev!
|
|
|
|
In the dischord chat I started an unofficial pool. I realized that even myself I need a larger pool to try and get big stakes. I bought in 181k new coins today to start it. The goal is to get to 500k and stake daily POOL Details: www.[Suspicious link removed]/myfrogger_pool EDIT: TINY DOT CC /myfrogger_pool I invite you into discussion at the discord. I am not active here on this forum. https://discordapp.com/channels/358221005468205066/ |
|
|
|
My downloaded wallet has only received 670 bytes of data. It doesn't appear to be downloading anything yet. Thoughts?  EDIT: I checked the log file and see there was an error. I had to go discordapp for help and can use the search feature. EDIT2: Wallet syncs FAST if it's set up correctly. Once I got it working I was synced in easily 30 min (so fast I wasn't watching it closely). You'll see it working because it says XX number of weeks behind. |
|
|
|
|
When waiting to sync, what exactly is going on? Is my computer processing something? Am I simply waiting in line for the others before me? I thought the value of a block chain is that the other's participating in this coin will be syncing each other.
|
|
|
|
|
Newbie poster here. I'm having the same issue "out of sync"....it's been 24 hours. Just a data point for everyone.
|
|
|
|
|
