Bitcoin Forum
September 30, 2022, 11:16:32 PM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 [14] 15 »
261  Bitcoin / Bitcoin Technical Support / Cannot synchronize with Bitcoin in testnet mode - No block source available on: January 29, 2014, 04:25:11 AM
I downloaded Bitcoin-QT for Windows 7 into:

MYUSERNAME/Downloads/bitcoin-0.8.6-win32/bitcoin-0.8.6-win32

I want to run Bitcoin in testnet mode, so I created bitcoin.conf with only the following content:

testnet=1

I put copies of bitcoin.conf into the following folders:

MYUSERNAME/Downloads/bitcoin-0.8.6-win32/bitcoin-0.8.6-win32
User/MYUSERNAME/AppData/Roaming/Bitcoin


When I double clicked on the Bitcoin-QT icon to execute the following, Bitcoin-QT starts up but it does not appear to be in testnet mode.

MYUSERNAME/Downloads/bitcoin-0.8.6-win32/bitcoin-0.8.6-win32/bitcoin-qt.exe

Can anyone tell me why it does not seem to go into testnet mode?

I went to Start > cmd to get the DOS prompt. I entered the following and it worked:

C:\User\MYUSERNAME\Downloads\bitcoin-0.8.-win32\bitcoin-0.8.6-win32>bitcoin-qt.exe -testnet

Bitcoin-QT launches in testnet mode. However, it is not synchronizing with the network. At the bottom of the Bitcoin-QT window, it shows:

"No block source available...155 weeks behind"

I tried adding the following to bitcoin.conf and restarted bitcoin-qt.exe -testnet but it didn't make any difference.

addnode=1.2.3.4
checklevel=2


After a few hours, it still shows "No block source available...155 weeks behind". How do I get this to synchronize?

Note that I am running Bitcoin-QT in Windows 7, which is running in VirtualBox, which is running in my Mac OSX. There seems to be no issue with any firewall in Windows 7 as my browser works fine. I have LittleSnitch running on my Mac, which tells me if a program is trying to access the internet. It told me that Bitcoin on my Mac and a program on Windows tried to access the internet, which I allowed. On my Mac, my Bitcoin-QT (in testnet and mainnet) synchronized fine. On Windows, Bitcoin-QT for mainnet, but not testnet, can synchronize.

User/MYUSERNAME/AppData/Roaming/Bitcoin/testnet3/debug has a lot of messages. Do these provide any clues?
2014-01-26 01:15:49 trying connection 93.93.135.12:18333 lastseen=149.6hrs
2014-01-26 01:15:51 No valid UPnP IGDs found
2014-01-26 01:15:51 upnp thread exit
2014-01-26 01:15:54 connection timeout
2014-01-26 01:15:54 trying connection testnet-seed.bluematt.me lastseen=0.0hrs
2014-01-26 01:15:59 connection timeout
2014-01-26 01:16:04 trying connection testnet-seed.bitcoin.petertodd.org lastseen=0.0hrs
262  Bitcoin / Bitcoin Technical Support / Re: Bitcoin-QT crashes when any bitcoin.conf file exists on: January 25, 2014, 06:09:40 PM
I found the cause of the problem.  bitcoin.conf was a rich-text file.  TextEdit tends to save files in rich-text format.  After I changed it to plain text format, problem is solved.
263  Bitcoin / Bitcoin Technical Support / Re: Bitcoin-QT crashes when any bitcoin.conf file exists on: January 20, 2014, 11:08:30 PM
Well, what are those "Problem Details"?

The problem details are shown by the Mac OSX as it does with any other application that crashes.  It contains a lot of system data.  I don't know if some of it opens up my system to hackers, especially the "threads" and "binary images", by publishing it to the public.  Below is the "problem details" but I removed some of the data, especially the "threads" and "binary images".  Have you been able to debug these crashes on a Mac by looking at this data?  If so, let me know if you need the "threads" and "binary images" and I'll research into whether this data is sensitive/private or not and then I'll send it you.

However, if you have a Mac, you should be able to reproduce this problem, as others have, by launching Bitcoin-QT with the bitcoin.conf file in your Library/Application Support/Bitcoin folder.  When you reproduce the problem, your Mac will show you your "Problem Details".

Thanks.

Quote


Process:         Bitcoin-Qt [5412]
Path:            /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
Identifier:      org.bitcoinfoundation.Bitcoin-Qt
Version:         0.8.6 (0.8.6)
Code Type:       X86 (Native)
Parent Process:  launchd [270]

Date/Time:       2014-01-19 20:25:00.846 -0600
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          42306752 sec
Crashes Since Last Report:           168
Per-App Interval Since Last Report:  103165 sec
Per-App Crashes Since Last Report:   9
Anonymous UUID:                      XXXXXXXXXXXXXXXXXXXXXXXXXXXX

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib                0x99XXXXXX kevent + 10
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Thread 1:  Dispatch queue: com.apple.libdispatch-manager
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Thread 2:
0   libSystem.B.dylib                0x99XXXXXX __workq_kernreturn + 10
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Thread 3:  com.apple.CFSocket.private
0   libSystem.B.dylib                0x99XXXXXX select$DARWIN_EXTSN + 10
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000000  ebx: 0x99c57693  ecx: 0xbfffec8c  edx: 0x99baec5a
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Binary Images:
    0x1000 -   0xXXXXXXX +org.bitcoinfoundation.Bitcoin-Qt 0.8.6 (0.8.6) <XXXXXXXXXXXXXXXXXXXXXXXXXXXX> /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
XXXXXXXXXXXXXX
XXXXXXXXXXXXXX

Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 8 GB, SMC 1.69f4
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 5.100.198.104.5)
Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: APPLE SSD TS512C, 465.92 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: Hub, 0x0424  (SMSC),
USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.),
USB Device: Bluetooth USB Host Controller,
USB Device: Apple Internal Keyboard / Trackpad,
USB Device: FaceTime HD Camera (Built-in),
USB Device: Hub, 0x0424  (SMSC),
USB Device: IR Receiver, 0x05ac  (Apple Inc.),
264  Bitcoin / Bitcoin Technical Support / Bitcoin-QT crashes when any bitcoin.conf file exists on: January 20, 2014, 02:34:06 AM
I am running Bitcoin-QT v0.8.6 on my Mac OSX 10.6.8.

If I do not have the bitcoin.conf file in the Library/Application Support/Bitcoin folder, then Bitcoin-QT will launch successfully.  However, if I do have the bitcoin.conf file, even if it is empty or if all of the lines are commented out, Bitcoin-QT will not launch.  Instead, the Mac shows a pop-up that states: "Bitcoin-QT quit unexpectedly.  Click Reopen to open the application again.  This report will be sent to Apple automatically.  Problem Details and System Configuration data"

If I rename or delete the bitcoin.conf file, then Bitcoin-QT launches successfully.

Does anyone have any idea of how to fix this or get past this?
265  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 18, 2014, 05:55:24 PM
We solve the wallet backup problem by keeping a copy of the private keys in the database.  For now, we're using the account system with thousands of accounts and tens-of-thousands of transactions without issue.  We have a secondary ledger than uses walletnotify and blocknotify to stay in sync.  We still use the bitcoin account system as the place of record, but our side-by-side tests have been perfect so far.  We could move off of the built-in account system if we needed to.  But you asked the easiest way to do some testing - not the most robust  Smiley
FWIW, this is also our cold-storage strategy.  When a user logs in, we push funds from the holding account into their account so they can play.  When they logout, we move it back to the holding account.  Then, we only keep a percentage of the total funds in teh holding account to support the numebr of people on the site at any given time.  This means if we got a rush of users, we would need to turn some away.  If only that would happen  Smiley

You're right that I should worry only about the minimum viable product and the easiest way to process bitcoins.  Just out of curiosity though, what do you plan to do when you get thousands of customers?

When you get a rush of users, then I assume that this becomes an issue only if they all want to withdraw bitcoins.  I assume that if your holding account runs out of bitcoins, then you can tell your users to wait as you manually move some bitcoins from your cold (which I assume is the same as offline) storage?

That sounds about right.  Note that you can do all of that without writing any software.  *notify can just be echos to a text file.  Also, bitcoind is a commandline version of the api, so you can do bitcoind getinfo, or bitcoind listtransactions, etc. to test out the api.

That's good to know.

We user sendFrom so they funds are removed from the users account, rather than the wallet.

According to tgerring's posting at https://bitcointalk.org/index.php?topic=300632.0:
Quote
Use Gavin's contrib/spendfrom script, never the `sendfrom` command

I don't know why he wrote the above.  I assume that you haven't had any problems with sendfrom.

Pretty close.  We create a new account for the user, then use walletnotify to watch for deposits.  When a deposit comes in, it's "unverified".
We then use blocknotify to watch for new blocks.  When a block comes in, we check the balance of the users account with 0 confirmations, then again with 4 confirmations.  The delta is their "unconfirmed" balance.
We don't do the sweep currently on the live site, but that's how we handle cold storage.

I don't understand what you mean by:  "We don't do the sweep currently on the live site".  Can you explain or elaborate?

It's not obvious. 
You can call getbalance and pass in the number of confirmations you want.  So if a user has 10 confirmations on their first 1btc deposit, and 2 confirmations on their second 5btc deposit:
getbalance 0 confirmations = 6btc
getbalance 4 confirmations = 1btc
From that, we can calculate that they have a balance of 1btc, and an additional 5btc unconfirmed.

So then blocknotify is only used to say, "A new block was received, and users' confirmations may have changed." 
We just use it to trigger a re-check of the users that have unconfirmed funds.  If the confirmed and unconfirmed balances are the same, we can stop checking their account with each new block.

Let me reiterate what you wrote above to fully understand what you are doing.  You keep track of users (in your database) who have unconfirmed funds.  When a blocknotify comes in, you call getbalance for each and every one of your users who have unconfirmed funds, to find out if these users still have or no longer have unconfirmed funds.  For users who no longer have unconfirmed funds, you write into your application database to indicate this, so that your application can tell your user that he has more bitcoins to play with.  Do I have this right?

Don't the blocknotify come in quite often, especially if you have thousands of users?  I'm assuming that blocknotify will run every time there is a confirmation on each and every transaction for every one of your users.  There could eventually be thousands of confirmations on a transaction.  Here's a possible number of blocknotifies:
1,000 confirmations X 5 deposits X 1,000 users = 5,000,000 blocknotifies.  For each of these blocknotifies, you are checking all of your users with unconfirmed funds.  This means you can be running getbalance 2,500,000,000 times (5m X 500) if you have 500 users with unconfirmed funds.  This seems like a lot of processing.  Do I have this wrong?

Only run on testnet.  There's no need to run on mainNet until you're getting close to launch. 
I'm happy to answer questions.  Just know that you're only getting one team's opinion.  There are a million ways to do things  Smiley

When we launch, do we need to run SSL on mainNet (assuming mainNet refers to regular bitcoins)?  Why is SSL needed?  What data needs to be encrypted?

Virtual Keyboard and Mouse.  A well known bitcoin casino had their data center's maintenance site hacked.  Someone put in an order to have a VKM installed.  The machine rebooted and the attackers attempted to use the vkm to get console access.  Thankfully, the casino used full-disk encryption, so reboots required a manual password step. 
Attackers in this space are really, really clever.

It's amazing how much less productive and wealthy our economies are due to all of the extra work and money we have to spend to protect ourselves from hackers, criminals, etc.  Also, the adoption of bitcoin would be much more widespread if it wasn't for these hackers and criminals.

266  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 18, 2014, 03:52:34 AM
Once you have the blockchain/bitcoin integration (again, they're basically the same), the effort of moving to a local wallet is:
1)  Install the client and configure it to run as a server (minimal work)
2)  Understand the security implications of having a local wallet, cold storage, etc.  You'll have security work with an outsourced partner as well, so I don't think this work is really incremental.

It was suggested to me that when users withdraw, I should send bitcoins to users manually from an offline wallet.  I was thinking of using Armory to do this and to install an Armory Watching-only wallet (https://bitcoinarmory.com/about/using-our-wallet/) on the server.  Have you looked into this?  Did you use Armory's offline wallet for your "cold storage"?

Did you automate the sending of bitcoins to users?

I read up on https://en.bitcoin.it/wiki/Accounts_explained.  It states: 
Quote
Wallet backups are an issue; if you rely on a good backup of wallet.dat then a backup must be done every time an address is associated with an account and every time the 'move' command is used.
The accounts code does not scale up to thousands of accounts with tens of thousands of transactions, because by-account (and by-account-by-time) indices are not implemented. So many operations (like computing an account balance) require accessing every wallet transaction.
Most applications already have a customer database, implemented with MySQL or some other relational database technology. It is awkward at best to keep the bitcoin-maintained Berkely DB wallet database and the application database backed up and synchronized at all times.

Armory claims that one backup of their wallet is good enough forever.  I wonder if their wallet backups have the same issue as stated above.

If the accounts code does not scale up to thousands of accounts, then what are you going to do if you get thousands of customers?

Do you try to synchronize your database with Bitcoin's wallet database?

Thanks for your help and suggestions.  I think I got my work cut out for me.  I will do the following:

  • Install Armory
  • Add walletnotify and blocknotify options in bitcoin.conf
  • Get Testnet coins from faucets
  • Run Bitcoind with testnet=1 in bitcoin.conf
  • Try executing Bitcoin API and Account commands and send Testnet coins to myself

https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list shows a list of "Typical Uses".  It doesn't explain how to send bitcoins to a customer, to enable the customer to withdraw.  Do you use sendtoaddress?

According to https://bitcointalk.org/index.php?topic=300632.0, we should do this:
  • Create a new account for each user to accept deposit from with getaccountaddress
  • Then have a daemon that checks listsinceblock for any deposits.
  • If deposit is found, use move to transfer the balance to the "bank" account and credit the user.
  • Then the next time listsinceblock is called, they will show up as 0.
  • All outgoing withdraw is sent via move from "bank" account to withdraw address.

Is the above what you did?  Am I correct to assume that you use walletnotify and blocknotify instead of "a daemon that checks listsinceblock for any deposits"?

I cannot find out anywhere how blocknotify tells me that a particular transaction is confirmed.  Am I correct to assume that I will receive data from blocknotify once I test with Testnet coins and this data will contain the transaction ID (from which I can use gettransaction <txid> to get the customer's account, address and amount)?

Do I need SSL to run Testnet or main Bitcoin network?

According to http://www.ideaexcursion.com/2013/09/18/developing-against-bitcoind/:  "working with Bitcoin can be EXCRUCIATINGLY difficult" and there are a lot of things to do when using it.  I think the adoption of Bitcoin for consumers and sellers of services/goods will be much more widespread if Bitcoin was easier.  Hopefully, I can ask you more questions if I run into difficulty.

Know that your server will be attacked, your faucet will be drained, your games will be botted, your service provider will let people in to your datacenter to install VKMs, etc.

What are VKMs?  Virtual Knowledge Managers?  What harm can they do?
267  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 17, 2014, 06:11:09 PM
So we recently went through this when developing MooCoin.

Thanks for your posting.  It is very interesting, as your experience is similar to what I'm trying to do.  Your suggestions sound very good.

To simplify our lives, we would rather use Bitpay or Coinbase.  Even though our game requires skill, there is still an element of chance, hence it can be deemed as gambling.  Therefore, Coinbase and Bitpay won't help us.  Am I correct to assume that your game is deemed as gambling and that's why you had to use bitcoind or Blockchain?

How much extra work was it to get bitcoind and wallet running on your server, versus Blockchain.info's API?

Have you ever looked at using MtGox or any of the "Merchant Services" (payment processors) listed at https://en.bitcoin.it/wiki/How_to_accept_Bitcoin,_for_small_businesses and https://en.bitcoin.it/wiki/Merchant_Howto?

Second, start by really understanding the bitcoin account system in the reference client, and using it.

When you say "bitcoin account system", are you referring to the "Original Bitcoin client/API calls list" (https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list)?

Did you start with this tutorial?:  https://en.bitcoin.it/wiki/PHP_developer_intro

look at the walletnotify and blocknotify options in the bitcoin.conf.

I don't have bitcoin.conf on my Mac, but I do have bitcoin-temp.conf.  I do not have walletnotify or blocknotify in my bitcoin-temp.conf, but I found this:  https://bitcointalk.org/index.php?topic=203438 which explains how to use walletnotify, but it sounds complicated.

I checked out MooCoin.  What is the difference between the address in the personal URL and the public account ID?

Unlike MooCoin, our users are already registered with usernames.  Am I correct to assume that we should assign a different bitcoin address to each user for them to make deposits to, and re-use the address when the user wants to make subsequent deposits?  (I assume that when our users wants to withdraw, we should prompt him/her for his/her bitcoin address, store it and use it for future withdraws.)

The Bitcoin community is really turning a corner for the better, but there's still a large portion of people that are remnants of the bad old days.  Hacking attempts, scams, etc are rife in this community.  Just be careful.

The users on the bitcoin forums seem like they are trying to be helpful.  What are they are trying to scam or hack?
268  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 17, 2014, 02:20:58 AM
IPN i mean the callbackurl.
By triggering cron I mean the cron script, a subset of it, not an actual cron.

No on player registration. The receive api forwards bitcoin, it doesn't store it.

When I wrote "cron", I was referring to your statement about cron:  You wrote: "Your cron would loop through all your player addresses, then loop through all their payments and make sure you got them all."  Aren't you referring to a cron script?  Why would the ipn trigger the cron script if the cron script is supposed to run every hour?

Why would I assign an address to players upon their registration on our site?  Assign the address to whom?  I don't know what you mean by "On registration you assign an address with the receive api".  My understanding of how the Blockchain.info's Receive Payment API works is this:  When my player wants to deposit bitcoin, I call the Blockchain API, providing my receive address.  The API returns a receive address (that belongs to Blockchain), that I show to my player, so that my player can send bitcoin to that address.  After the player sends bitcoin to that address, Blockchain forwards the bitcoin to my receive address.  The next time the same player wants to deposit money again, I call the Blockchain API again, providing my receive address, and the API provides another (different) receive address (which belongs to Bockchain), which I show to my player.  So, each time a player wants to send bitcoin to me, the player is sending to a different address provided by Blockchain.
269  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 17, 2014, 01:51:19 AM
You would use https://blockchain.info/q/getreceivedbyaddress and loop through transactions making sure you got them all. Set it to a few confirmations.

Your cron would loop through all your player addresses, then loop through all their payments and make sure you got them all. Database is easy due to transaction ids.

Your ipn would trigger the second part.

On registration you assign an address with the receive api. But remember this address has to work forever in case they store it, so forward it knowing that.

Thanks.  You wrote "Your ipn would trigger the second part.".  What is ipn?  instant payment notification?  What second part are you referring to?  The "cron"?  If so, why would the ipn trigger the cron if the cron is supposed to run every hour?

You wrote: "On registration you assign an address with the receive api."  Are you referring to my registration with Blockchain?  I don't know what you mean by "forward it".
270  Economy / Service Discussion / Review of Blockchain.info's Receive Payment API on: January 16, 2014, 06:50:38 PM
We are building an online game and want to enable our users to play for bitcoins.  Since we don't know how popular bitcoins will be with our players, we are seeking an easy way to enable our users to deposit and withdraw bitcoins.  Even though our game is skill-based, there is an element of chance, hence it can be deemed as gambling.  Therefore, Bitpay and Coinbase won't help us.

It seems that Blockchain.info's Receive Payment API is the easiest way to start, to enable our users to deposit.  Then we'll manually send bitcoins when users want to withdraw.  (I welcome suggestions on other methods that are as easy or easier.)  However, there are comments about how Blockchain can fail or be slow in responding (to the callback URL?), such as:


I'm reluctant to think that the above comments confirm that Blockchain was or still is unreliable.  I've stayed at hotels where commenters on Tripadvisor wrote negative reviews, but I did not see the same negative aspects.  Has Blockchain resolved most of the above issues since they were posted?  I'm interested in reading from people who have had positive and negative experiences with Blockchain.info's Receive Payment API.  Is Blockchain.info's Receive Payment API reliable, fast and trustworthy enough?
271  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 16, 2014, 05:51:19 PM
You should be aware that security is pull only. So even if they push a notification, you must also pull. You can also bulk pull hourly to catch missed payments.

I'm not sure what you mean by "security is pull only".

How do we pull?  I checked out the following from Blockchain.info:


The closest or most relevant thing to what you are talking about, that I can find is their "Single Address" JSON API, or specifically:  http://blockchain.info/address/$bitcoin_address?format=json  I think it shows the following as their JSON response?

{
   "hash160":"660d4ef3a743e3e696ad990364e555c271ad504b",
   "address":"1AJbsFZ64EpEfS5UAjAfcUG8pH8Jn3rn1F",
   "n_tx":17,
   "n_unredeemed":2,
   "total_received":1031350000,
   "total_sent":931250000,
   "final_balance":100100000,
   "txs":[--Array of Transactions--]
}

However, I do not see how the above enables me to pull security.
272  Economy / Service Discussion / Re: Blockchain.info Receive Payment API on: January 16, 2014, 05:22:47 PM
Did you ever get a resolution to this?

I have no experience with Blockchain.info's Receive Payment API, but people told me that they can fail or be slow.  I'm thinking of using it to accept payments, but now I'm wary.  Have you had bad experience with this?
273  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 16, 2014, 01:47:55 PM
The best idea would be using the bitcoin API call list.
you can also use blockchain.info but if you should know that sometimes they fail to send the notification or send it much later then the actual transaction took place,
so basically using a blockchain is a single failure point.

Thanks for your input and warning.  We don't know how popular bitcoins will be with our players, so we want to build the minimum viable product initially.  Besides, it seems that using the bitcoin API call list seems much more complicated.  With Blockchain.info, I assume that you are referring to our callback URL that they will post to.  Would you know how often Blockchain.info has failed or been late in sending the notifications to the callback URL?  Have you had experience in using Blockchain.info's "receive payment API"?
274  Bitcoin / Bitcoin Technical Support / Re: Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 15, 2014, 11:00:21 PM
Yes, it will, but it's not economical. the reason is that the transaction for consolidating all the dust will still be large (in size), so you will still have to pay a fee. furthermore, the fee you pay to consolidate the dust will be the same as the fee for spending the dust in a normal transaction. Therefore you're not making any savings by sending all your dust to one address.

Let's say I do the following:

1.  Install Armory.
2.  Send all of my bitcoins, which will include the dust amounts, in one transaction from my Bitcoin-QT wallet to my Armory wallet, and pay the transaction fee.

After doing the above, am I correct to assume that my Armory wallet should not have any dust transactions?  When I want to send/spend normal amounts of bitcoins (such as 0.001 BTC or 0.0001 BTC) from my Armory wallet, am I correct to assume that I should not be charged a transaction fee because I do not have dust transactions in my Armory wallet?
275  Bitcoin / Bitcoin Technical Support / Re: Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 15, 2014, 03:31:46 PM
You could do manual coin control and always put one or two dust outputs with your regular transactions that you pay a fee for.

Thanks for your suggestion.  I searched for "manual coin control of bitcoin" but couldn't find anything relevant to this.  Can you provide a link or explanation of how to do this?
276  Bitcoin / Bitcoin Technical Support / Re: Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 15, 2014, 12:25:51 AM
Is there any way of consolidating these dust amounts without paying the transaction fee?

You can try sending the transaction without a fee and hope for the best - it could take a day or more though. And it's possible that the transaction is never mined into a block.

Thanks for your input.  How can I try to send the transaction without a fee?  Bitcoin-QT tells me there is a fee and it shows only two buttons:  Cancel or Yes.

What does it mean if the transaction is never mined into a block?  Does it mean that I will lose the bitcoins in that transaction?
277  Bitcoin / Bitcoin Technical Support / Re: Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 14, 2014, 07:23:33 PM
Yes, it will, but it's not economical. the reason is that the transaction for consolidating all the dust will still be large (in size), so you will still have to pay a fee. furthermore, the fee you pay to consolidate the dust will be the same as the fee for spending the dust in a normal transaction. Therefore you're not making any savings by sending all your dust to one address.

Thanks for your input.  These dust transactions are much more of pain than they are worth.  There should be warnings everywhere that these faucets give out micro amounts and these micro amounts will cost you way more in fees to spend them, than they are worth.  I thought these faucets were originally there to let people dip their toes in the Bitcoin water or to get some bitcoins for free first in order to test them out.  Instead, they seem more of a scam by malicious dicks.  Am I wrong?

Is there any way of consolidating these dust amounts without paying the transaction fee?
278  Bitcoin / Bitcoin Technical Support / Re: Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 14, 2014, 04:24:08 PM
Yes they'd combine.

There's also this
https://github.com/petertodd/dust-b-gone

Thanks for your answer.  Will there be a transaction fee to doing it the Armory way or the dust-b-gone way?
279  Bitcoin / Bitcoin Technical Support / Re: Easiest way to accept BTC and test on: January 13, 2014, 01:29:09 AM
Ok keep it simple, use a hot wallet all around. Minimum viable product. Until it gets to an amount you can't insure, move on. I'm available for consulting and programming.

There's also mtgox which probably won't care if you don't do fiat. Or btce. Exchanges might be better since withdrawing is more separated.

Sorry, I'm confused.  I thought using Blockchain.info's "receive payment API" is simpler.  How is the hot wallet simpler than Blockchain?

Thanks for suggesting MtGox.  I found this:  https://www.mtgox.com/merchant  and I sent them an inquiry on whether they will work with gambling sites and for more information on how to use their Payment Gateway.

What is "btce".  I found https://btc-e.com/ which is an exchange but doesn't seem to provide payment processing.

280  Bitcoin / Bitcoin Technical Support / Eliminate Dust transactions by sending every BTC from one wallet to another? on: January 12, 2014, 07:57:25 PM
Most of my initially received bitcoins were from faucets and therefore, these ended up being dust transactions. Since then, I've bought some bitcoins which are not dust.

Now I'm trying to send 0.0005 BTC to test out Blockchain.info's "receive payment API" (http://blockchain.info/api/api_receive) PHP example (https://github.com/blockchain/receive_payment_php_demo).  But Bitcoin-QT is telling me that I must pay 0.0005 BTC transaction fee.

I found out that the fee is due to the dust transactions.  Now, I like to get rid of these dust transactions by combining their amounts.  Can anyone suggest an easy way to do this?

I was thinking of installing Armory and then transferring all of my bitcoins from my Bitcoin-QT wallet, in one transaction, to my Armory wallet.  Will this eliminate the dust transactions by combining all of my dust amounts together?  Will my new Armory wallet contain just one input transaction, and not over a dozen transactions of small amounts?
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 [14] 15 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!