Bitcoin Forum
May 24, 2024, 11:54:35 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 [104] 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 ... 165 »
2061  Other / CPU/GPU Bitcoin mining hardware / Re: Is mining with low power 1155 Celeron Efficient? on: July 10, 2012, 10:17:22 PM
Did someone say Celeron?

Certainly running one core will be more efficient than two, you don't have to drag another core along for the ride. You will get best efficiency by using the Intel Speedstep and making sure it is working by monitoring that the multiplier and voltage is automatically lowering when idle (CPU-Z is a good monitor for this). You may need to pick the laptop or power saver Windows power profile to enable it, along with having speedstep enabled in BIOS. Alternately, manually underclock - you can cut the CPU bus and system memory clocks in half yourself and undervolt the CPU by tweaking in BIOS.
2062  Economy / Gambling / Re: SatoshiDICE.com - The World's Most Popular Bitcoin Game on: July 10, 2012, 10:06:21 PM
Darn it, would have paid >5600BTC if I hit 0...
http://www.satoshidice.com/full.php?tx=abe865dc491e7ee95dec47bad1723d04bb3dc04d15040e40cec1af6799fc2aee

The URL http://satoshidice.com (with no www) is down, although there are many links to it all over the forum (including the first post).
2063  Economy / Lending / Re: Looking for a large-ish loan. on: July 10, 2012, 07:24:25 PM
If that's his real name, he ain't locked up anywhere that is 15 minutes from Boring OR:

http://www.mcso.us/PAID/Default.aspx
http://www.clackamas.us/safetyapp/inmates/
http://www.norcor.co/eagle/ICURRENT.HTM
2064  Bitcoin / Bitcoin Technical Support / Re: Formatted computer lost coins? on: July 07, 2012, 02:31:12 PM
The key phrase in the first post is "fresh install", that the OS was reinstalled and used after the formatting too, drastically reducing the chance of recoverable data remaining in unwritten areas.

If you do a quick format, which takes just a few seconds, then the majority of the data areas may still have been intact (until the reinstallation of another OS). If however a full format was done (10 minutes to several hours depending on the drive size and tech), this writes zeroes to all data areas of the hard drive, removing the option of recovery. This depends on how the OSX formatter's (appropriately called "erase disk") security option was set:

2065  Economy / Services / Re: WTS Demonoid Accounts - 23BTC for 23 Accounts! - 60% OFF! on: July 07, 2012, 01:46:28 PM
I would more crap on the thread because selling invite codes is prohibited by the site.

Please do not try to sell your invitation codes. It is against site policy. Thank you!
If someone you invite gets warned/banned, you might get warned/banned too.

When discovered, it will likely result in the OP's and all invited accounts being banned.
2066  Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator [v0.17] on: July 07, 2012, 12:36:38 PM
It's been a while since vanitygen has been updated.  I went through the earlier posts on this thread, and have tried to summarize the most common issues and feature requests:
...
The FAQ could certainly do a better job of explaining how to launch vanitygen.  Deepceleron, I really liked your earlier post, it has instructions that are very clear and concise.  If it's okay with you, I'd like to merge that into the FAQ.
Congrats on your return. You can use or re-purpose anything I wrote, with or without attribution. Thanks for your software!

Anything else?

When specifying a case-insensitive address prefix on the command line or in a text file list, you must still only use valid Base58 characters. This means you must only use lower-case i or o, and only upper-case L, or you will get an error.
  • Bad: 1celeron, 1CELERON
  • Good: 1ceLeron, 1CELERoN

This could be fixed so that if a case-insensitive search is being done, the user doesn't have to use correct case as input.
2067  Bitcoin / Press / Re: 2012-06-27 newscientist.com - Freicoin: Occupy's online currency for the 99 per on: June 28, 2012, 10:43:47 AM
"NASA Engineers", if the definition = an app developer with no degree listed under education, another app developer with a 2009 Society of Jesus physics degree  + two years as an app developer.

Quote
"are now hoping to crowdfund money - in US dollars - to fund development of the full system"
If only they could pay for more developers developers developers!?


2068  Other / Off-topic / Re: Bitcoin memes! on: June 27, 2012, 03:06:33 PM
Not sure if I inspired this thread, but there's this of course:

http://bitcoinmedia.com/using-memes-to-explain-bitcoin/

Here are a couple highlights:




















Samefont is same.
2069  Bitcoin / Development & Technical Discussion / Re: Help! I keep getting "Error: Transaction creation failed" on: June 25, 2012, 12:25:15 AM
Another possibility is that there is a larger fee required due to the current block size

Code misunderstanding detected:  The fees used in the generation of a txn have absolutely nothing to do with the current block size.
Wiki correction demanded then...

2070  Bitcoin / Bitcoin Discussion / Re: What if you could get paid in Bitcoin? on: June 24, 2012, 08:49:00 PM
I don't think minimum wage law recognizes the value of Bitcoin... so sure, pay me in Bitcoin to show me you don't have good legal counsel...

You would have to be paid in taxable government currency and then have it deposited in some employer credit union that allows you to withdraw in forex if you want.

There could be Bitcoin bonuses or such, but even that might be as taxable as when you get the gold watch when you retire.
2071  Other / Beginners & Help / Re: is it legal to sell otc drugs online? on: June 24, 2012, 08:09:24 PM
You would have to examine if it is a controlled/scheduled substance. Other rules may apply too. For example, spray paint is not illegal, but selling it to a minor in your state may be, same thing goes with the anti-meth-ingredient ID laws some states have for ephedrines. I think there are no laws prohibiting you from giving aspirin to someone, but the prilosec may have a 'non-prescription' dose that the prescription exceeds.
2072  Economy / Games and rounds / Re: [86 left] BFL Jalapeno Lottery - Win a 3.5 GH/s Mining ASIC! (0.25 BTC/ticket) on: June 24, 2012, 08:03:36 PM
Love the enthusiasm, but this just screams retarded. Selling tickets for an item you don't even own yet? Yippy, i can win a pre-order ticket....

Quote
The lottery operator is not associated with Butterfly Labs and will not take any responsibility if Butterfly Labs defaults, fails to deliver to specification or has any delays in shipping. The winner will have the order placed in his/her name and will be able to deal with BFL directly under these circumstances.

Meaning if bfl tanks after all this ends and you have your winning ticket, then your shit outta luck.

It would be a better raffle (lotteries can have no winner) if you just won 32BTC and can decide if you want to buy one. That wouldn't have the fancy name attached to the raffle to attract attention though...
2073  Bitcoin / Development & Technical Discussion / Re: Roadmap to 1.0? on: June 24, 2012, 07:29:51 PM
+ past the December block-reward-drops-to-25

 Shocked

I'm kind of surprised that even Gavin worries a bit about this.

It's not that he worries, it's just something that we need to prove as working in production.
There's a difference between testing something in a lab (testnet) and making it work in production ... we need to get this level of confidence.
You could make a 25BTC generate now and see if it crashes the network.... Testing is worth 25BTC, isn't it?
You'll have to wait to December to test that everybody orphans your 50BTC generate hack block though.

and also...
After we decide that it's out of beta, feature complete and tested, and we won't have any need to reset the blockchain back to block 0?
2074  Bitcoin / Development & Technical Discussion / Re: Help! I keep getting "Error: Transaction creation failed" on: June 24, 2012, 07:11:13 PM
Has an error been written to debug.log?

I would close and re-launch Bitcoin with the -rescan command line option so you can be sure your balances are correct (they may be in wrong change addresses etc, you may not see a balance problem in Bitcoin-qt.

Here is the code that seems to generate the error, the function SendMoney:

wallet.cpp
Code:
string CWallet::SendMoney(CScript scriptPubKey, int64 nValue, CWalletTx& wtxNew, bool fAskFee)
{
    CReserveKey reservekey(this);
    int64 nFeeRequired;

    if (IsLocked())
    {
        string strError = _("Error: Wallet locked, unable to create transaction  ");
        printf("SendMoney() : %s", strError.c_str());
        return strError;
    }
    if (!CreateTransaction(scriptPubKey, nValue, wtxNew, reservekey, nFeeRequired))
    {
        string strError;
        if (nValue + nFeeRequired > GetBalance())
            strError = strprintf(_("Error: This transaction requires a transaction fee of at least %s because of its amount, complexity, or use of recently received funds  "), FormatMoney(nFeeRequired).c_str());
        else
            strError = _("Error: Transaction creation failed  ");
        printf("SendMoney() : %s", strError.c_str());
        return strError;
    }

    if (fAskFee && !ThreadSafeAskFee(nFeeRequired, _("Sending...")))
        return "ABORTED";

    if (!CommitTransaction(wtxNew, reservekey))
        return _("Error: The transaction was rejected.  This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.");

    MainFrameRepaint();
    return "";
}

This seems to an error-catchall that the function CreateTransaction() failed, but not due to balance, fee, or file lock issues.

Something went wrong in here and it didn't return a true:

Code:

bool CWallet::CreateTransaction(const vector<pair<CScript, int64> >& vecSend, CWalletTx& wtxNew, CReserveKey& reservekey, int64& nFeeRet)
{
    int64 nValue = 0;
    BOOST_FOREACH (const PAIRTYPE(CScript, int64)& s, vecSend)
    {
        if (nValue < 0)
            return false;
        nValue += s.second;
    }
    if (vecSend.empty() || nValue < 0)
        return false;

    wtxNew.BindWallet(this);

    {
        LOCK2(cs_main, cs_wallet);
        // txdb must be opened before the mapWallet lock
        CTxDB txdb("r");
        {
            nFeeRet = nTransactionFee;
            loop
            {
                wtxNew.vin.clear();
                wtxNew.vout.clear();
                wtxNew.fFromMe = true;

                int64 nTotalValue = nValue + nFeeRet;
                double dPriority = 0;
                // vouts to the payees
                BOOST_FOREACH (const PAIRTYPE(CScript, int64)& s, vecSend)
                    wtxNew.vout.push_back(CTxOut(s.second, s.first));

                // Choose coins to use
                set<pair<const CWalletTx*,unsigned int> > setCoins;
                int64 nValueIn = 0;
                if (!SelectCoins(nTotalValue, setCoins, nValueIn))
                    return false;
                BOOST_FOREACH(PAIRTYPE(const CWalletTx*, unsigned int) pcoin, setCoins)
                {
                    int64 nCredit = pcoin.first->vout[pcoin.second].nValue;
                    dPriority += (double)nCredit * pcoin.first->GetDepthInMainChain();
                }

                int64 nChange = nValueIn - nValue - nFeeRet;
                // if sub-cent change is required, the fee must be raised to at least MIN_TX_FEE
                // or until nChange becomes zero
                // NOTE: this depends on the exact behaviour of GetMinFee
                if (nFeeRet < MIN_TX_FEE && nChange > 0 && nChange < CENT)
                {
                    int64 nMoveToFee = min(nChange, MIN_TX_FEE - nFeeRet);
                    nChange -= nMoveToFee;
                    nFeeRet += nMoveToFee;
                }

                if (nChange > 0)
                {
                    // Note: We use a new key here to keep it from being obvious which side is the change.
                    //  The drawback is that by not reusing a previous key, the change may be lost if a
                    //  backup is restored, if the backup doesn't have the new private key for the change.
                    //  If we reused the old key, it would be possible to add code to look for and
                    //  rediscover unknown transactions that were written with keys of ours to recover
                    //  post-backup change.

                    // Reserve a new key pair from key pool
                    vector<unsigned char> vchPubKey = reservekey.GetReservedKey();
                    // assert(mapKeys.count(vchPubKey));

                    // Fill a vout to ourself
                    // TODO: pass in scriptChange instead of reservekey so
                    // change transaction isn't always pay-to-bitcoin-address
                    CScript scriptChange;
                    scriptChange.SetBitcoinAddress(vchPubKey);

                    // Insert change txn at random position:
                    vector<CTxOut>::iterator position = wtxNew.vout.begin()+GetRandInt(wtxNew.vout.size());
                    wtxNew.vout.insert(position, CTxOut(nChange, scriptChange));
                }
                else
                    reservekey.ReturnKey();

                // Fill vin
                BOOST_FOREACH(const PAIRTYPE(const CWalletTx*,unsigned int)& coin, setCoins)
                    wtxNew.vin.push_back(CTxIn(coin.first->GetHash(),coin.second));

                // Sign
                int nIn = 0;
                BOOST_FOREACH(const PAIRTYPE(const CWalletTx*,unsigned int)& coin, setCoins)
                    if (!SignSignature(*this, *coin.first, wtxNew, nIn++))
                        return false;

                // Limit size
                unsigned int nBytes = ::GetSerializeSize(*(CTransaction*)&wtxNew, SER_NETWORK, PROTOCOL_VERSION);
                if (nBytes >= MAX_BLOCK_SIZE_GEN/5)
                    return false;
                dPriority /= nBytes;

                // Check that enough fee is included
                int64 nPayFee = nTransactionFee * (1 + (int64)nBytes / 1000);
                bool fAllowFree = CTransaction::AllowFree(dPriority);
                int64 nMinFee = wtxNew.GetMinFee(1, fAllowFree, GMF_SEND);
                if (nFeeRet < max(nPayFee, nMinFee))
                {
                    nFeeRet = max(nPayFee, nMinFee);
                    continue;
                }

                // Fill vtxPrev by copying from previous transactions vtxPrev
                wtxNew.AddSupportingTransactions(txdb);
                wtxNew.fTimeReceivedIsTxTime = true;

                break;
            }
        }
    }
    return true;
}

I would look at all the "return false" cases above and figure out if something about your transaction (balances, etc) might set off one of them. Another thing you can do to throw random ideas at the problem is create more reserve addresses starting Bitcoin with the command-line option bitcoin.exe -keypool=150.

Another possibility is that there is a larger fee required due to the current block size or size of inputs you are using, but a bug in the client isn't prompting for that, you could bump up the voluntary fee in the client to .01 and see if it goes.
2075  Bitcoin / Bitcoin Technical Support / Re: EXCEPTION: 11DbException Db::open: Invalid argument bitcoin in Run on: June 24, 2012, 06:43:05 PM
The debug log may give some indication of what is going on. One scenario if you are using the release client is that something is borked in your wallet database - when Bitcoin tries to update the wallet (writing something like the "last block seen" counter) it fails. The wallet file may corrupted, but could also be locked by another Bitcoin process or left unwriteable or without correct permissions by something with the operating system. You also may have a bad area of your hard drive or other such hardware problem - writing to the same bad sectors when attempting to erase and re-download the blockchain gets you the same database error. It would be worth the time to make another wallet.dat backup of your current wallet, and do a hard drive surface scan.

There a few things other things you can do to discover the problem:
- delete the blockchain database and rename the wallet (or just rename the whole bitcoin data directory), and see Bitcoin get all the blocks normally,
- restore an older wallet backup and see if the problem returns,
- use a blockchain download, and do a rescan with your current wallet and see if the error crops up.
2076  Bitcoin / Pools / Re: High orphan rate and long confirmation time discussion on: June 24, 2012, 06:29:30 PM
There was a huge spike of orphans in April (around 10% of network blocks had orphan races, one orphan actually had several siblings), but BIP16 is not causing orphans anymore. Are you saying that left over tx from the BIP16 orphans are still yet to be completed and adding to the current average tx size increase?
If a miner tries to include the transaction above because they have not upgraded to BIP16, they will create a block that is not accepted by the network, other miners won't build on it. That transaction is still floating around on the network, the last time it was included in a block (getting the miner an orphan instead of 50 BTC) was a week ago.
2077  Bitcoin / Pools / Re: High orphan rate and long confirmation time discussion on: June 24, 2012, 05:26:25 PM
The last chart shows boxplots of the orphaned block size minus the related confirmed block size in kB (1e03). For the rare cases of more than one orphaned sibling, the mean was taken. This shows a significant change in the variance of the difference since BIP16 -  lots of small blocks competing against larger ones, sometimes winning and sometimes losing, although the median of the last difficulty period shows a skew toward orphans being larger than the related confirmed blocks.

My hypothesis was that larger blocks with more transactions would propagate more slowly and be more likely to be orphaned. The boxplot for the last difficulty period does lend some credence to the idea, but we'll have to wait another difficulty period or two to be sure.

Another explanation may be that some pools are making bocks with fewer transactions, and other pools aren't. This in itself may be creating random variance and not be related to the orphan production.

Any other ideas?
BIP16 caused a huge amount of orphans. All it took was for one person to push out a transaction to split the network, and some miners have still tried to include it this month:

http://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2
2078  Economy / Goods / Re: [WTB] Aeron Chair on: June 22, 2012, 04:33:31 PM
I guess you don't listen to PBS to know where to get your Herman Miller Aeron chair..., starts at $630 w free ship:
http://www.sit4less.com/products/Herman-miller/Aeronreg-chair-exclusive-true-black/93

For an additional $200, you can have a pimp bling chair:

It must be 1999 again, 20-something dot-com billionaires and Aeron chairs...
2079  Other / Beginners & Help / Re: Newbie Mtgox to Dwolla help! on: June 20, 2012, 05:06:31 AM
Par for the course:
  • Transfer bitcoins to mtgox, wait 1-2 hours
  • buy USD
  • withdraw USD to Dwolla
  • Your funds are now surprise locked until you mail a notarized, apostilled valid copy of a government issued photo ID and proof of residence (less than 3 months old) - E.g. A utility or phone bill to Japan. Week?
  • Withdraw to Dwolla, transfer time 2-3 weeks in limbo
  • Funds arrive in Dwolla, now Dwolla locks your funds and demands your ID, another week to verify
  • withdraw to bank account, ~5 business days.
2080  Bitcoin / Bitcoin Technical Support / Re: Blockchain Frozen on: June 20, 2012, 03:12:57 AM
Close Bitcoin, open terminal

cd ~/.bitcoin/
mv blk0001.dat blk0001.old
mv blkindex.dat blkindex.old
wget http://eu1.bitcoincharts.com/blockchain/blockchain-2012-06-20.tar
tar -xvf blockchain-2012-06-20.tar

Pages: « 1 ... 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 [104] 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 ... 165 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!