The LTB Network Forum

Would this work to minimize counterwallet fees?

Back to Metacoin Central

Comments

irnhnve

Offline
Posts: 228

If you were to sweep the private keys from multiple counterwallet addresses into the bitcoin-qt client, export the private key from the bitcoin-qt client and sweep it into a counterwallet address, would all of the assets that were associated with the original counterwallet addresses appear under one address after sweeping the bitcoin-qt private key?

I ask because, as far as I remember, I don't recall having bitcoin-qt prompt you to pay a fee for importing private keys. Counterwallet makes you pay a fee that increases for each asset being swept which can be quite high if you have many assets.

For me, it would cost over $1 in fees for each address even after excluding things like voting tokens. I'm trying to combine the balances for more than 10 separate addresses into one. I'd really prefer not to pay that much in fees if I can find a workaround.

Posted on February 23, 2015 at 6:48 PM

2 likes

• Cryptonaut

  

  Offline
  Posts: 1944
  Location: Canada

  Unfortunately there isn't any way to send multiple amounts of multiple counterparty tokens to another address in one transaction, just because it's simply too much data to hold in a BTC transaction.

  If your able to use the command line interface instead, you could setup a local copy of bitcoind (which you already have if you are running bitcoin-qt), import your private keys into there. Then you can set up a local counterparty node on top of bitcoind and use the command line options to customize the fees.

  Example command:

  python3 counterpartyd.py --multisig-dust-size 0.00001 --regular-dust-size 0.00001 --fee 0.00001 send --source [source_address] --destination [destination_address] --asset [token name] --quantity [amount]

  you can make the fees pretty much as low as you want, as long as you don't mind waiting extra long for them to confirm.

  Posted on February 23, 2015 at 8:53 PM
  Permalink
  6 likes
• irnhnve

  

  Offline
  Posts: 228

  @cryptonaut Unfortunately there isn't any way to send multiple amounts of multiple counterparty tokens to another address in one transaction, just because it's simply too much data to hold in a BTC transaction.

  If your able to use the command line interface instead, you could setup a local copy of bitcoind (which you already have if you are running bitcoin-qt), import your private keys into there. Then you can set up a local counterparty node on top of bitcoind and use the command line options to customize the fees.

  Example command:

  python3 counterpartyd.py --multisig-dust-size 0.00001 --regular-dust-size 0.00001 --fee 0.00001 send --source [source_address] --destination [destination_address] --asset [token name] --quantity [amount]

  you can make the fees pretty much as low as you want, as long as you don't mind waiting extra long for them to confirm.

  I'll definitely give this a shot, thanks!

  Posted on February 24, 2015 at 8:44 AM
  Permalink
  0 likes
• bujank

  

  Offline
  Posts: 397
  Location: indonesia

  fee coiunterwallet is big. i am move to poloniex fee minimal

  Posted on February 25, 2015 at 9:32 PM
  Permalink
  0 likes
• pooktwo

  

  Offline
  Posts: 792
  Location: Indianapolis

  @cryptonaut Unfortunately there isn't any way to send multiple amounts of multiple counterparty tokens to another address in one transaction, just because it's simply too much data to hold in a BTC transaction.

  If your able to use the command line interface instead, you could setup a local copy of bitcoind (which you already have if you are running bitcoin-qt), import your private keys into there. Then you can set up a local counterparty node on top of bitcoind and use the command line options to customize the fees.

  Example command:

  python3 counterpartyd.py --multisig-dust-size 0.00001 --regular-dust-size 0.00001 --fee 0.00001 send --source [source_address] --destination [destination_address] --asset [token name] --quantity [amount]

  you can make the fees pretty much as low as you want, as long as you don't mind waiting extra long for them to confirm.

  Is this something that could be implemented with the asset distributor as an option to make the fees lower? Like lets say there could be an option that allows you in the distributor to set your own fee you wish to pay?

  Posted on February 26, 2015 at 5:19 AM
  Permalink
  0 likes
• adam

  

  Offline
  Posts: 1980
  Location: California, USA

  @pooktwo

  @cryptonaut Unfortunately there isn't any way to send multiple amounts of multiple counterparty tokens to another address in one transaction, just because it's simply too much data to hold in a BTC transaction.

  If your able to use the command line interface instead, you could setup a local copy of bitcoind (which you already have if you are running bitcoin-qt), import your private keys into there. Then you can set up a local counterparty node on top of bitcoind and use the command line options to customize the fees.

  Example command:

  python3 counterpartyd.py --multisig-dust-size 0.00001 --regular-dust-size 0.00001 --fee 0.00001 send --source [source_address] --destination [destination_address] --asset [token name] --quantity [amount]

  you can make the fees pretty much as low as you want, as long as you don't mind waiting extra long for them to confirm.

  Is this something that could be implemented with the asset distributor as an option to make the fees lower? Like lets say there could be an option that allows you in the distributor to set your own fee you wish to pay?

  Fees are set platform-wide at the moment since they are fee instructions to the distributor, and the cost in the distributor is already about as low as we found it to be still reliable. In the future we will have multiple pricing models, per-tx fee for normal users and no or very low per tx fee for users with appropriate rolecoins

  Posted on February 26, 2015 at 7:50 AM
  Permalink
  1 like
• pooktwo

  

  Offline
  Posts: 792
  Location: Indianapolis

  @adam

  @pooktwo

  @cryptonaut Unfortunately there isn't any way to send multiple amounts of multiple counterparty tokens to another address in one transaction, just because it's simply too much data to hold in a BTC transaction.

  If your able to use the command line interface instead, you could setup a local copy of bitcoind (which you already have if you are running bitcoin-qt), import your private keys into there. Then you can set up a local counterparty node on top of bitcoind and use the command line options to customize the fees.

  Example command:

  python3 counterpartyd.py --multisig-dust-size 0.00001 --regular-dust-size 0.00001 --fee 0.00001 send --source [source_address] --destination [destination_address] --asset [token name] --quantity [amount]

  you can make the fees pretty much as low as you want, as long as you don't mind waiting extra long for them to confirm.

  Is this something that could be implemented with the asset distributor as an option to make the fees lower? Like lets say there could be an option that allows you in the distributor to set your own fee you wish to pay?

  Fees are set platform-wide at the moment since they are fee instructions to the distributor, and the cost in the distributor is already about as low as we found it to be still reliable. In the future we will have multiple pricing models, per-tx fee for normal users and no or very low per tx fee for users with appropriate rolecoins

  Makes sense. Thanks :)

  Posted on February 26, 2015 at 3:55 PM
  Permalink
  0 likes
• adam

  

  Offline
  Posts: 1980
  Location: California, USA

  You can't reduce fees in counterwallet at this time

  Posted on April 22, 2015 at 4:42 PM
  Permalink
  0 likes

Post Reply