Bitcoin Forum
May 27, 2024, 05:29:52 AM *
News: Latest Bitcoin Core release: 27.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 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 [34] 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 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 ... 162 »
661  Economy / Goods / Re: [WTS] HUGE tracts of land! OK, 3.3 acres at least. on: March 27, 2013, 08:57:57 PM

It has come to my attention that Lot #11 was mispriced, and is actually being sold below cost.

The new price for Lot #11 is $33,000 (or bitcoin equivalent).  The other prices are unchanged.

Snapshot, based on $87.99 current price:

     Both lots ($70,000):  795 BTC
     Lot #5 alone ($45,000):  511 BTC
     Lot #11 alone ($33,000):   375 BTC

662  Bitcoin / Development & Technical Discussion / Re: Creating an "official" protocol specification for the Bitcoin internet currency on: March 27, 2013, 01:48:29 AM

There is already plenty of work here:

     https://en.bitcoin.it/wiki/Protocol_specification

and here:

     https://en.bitcoin.it/wiki/Bitcoin_Improvement_Proposals

663  Bitcoin / Bitcoin Discussion / Re: Idea: Collateralized Identity – Using bitcoin to suppress sockpuppets on: March 26, 2013, 06:22:48 AM

It can be useful to prove someone controls a certain amount of bitcoin balance, using the sign message feature.

But it is also useful to consider a fresh transaction, that intentionally "burns" a specific amount of money by giving it to the miner as a transaction fee.  This helps support a public service -- bitcoin transaction validation -- while assuring that real cost, real effort was spent to create an identity.

The keys used to spent the bitcoins in question provide another sign-message entry point.

664  Bitcoin / Bitcoin Discussion / Re: Idea: Collateralized Identity – Using bitcoin to suppress sockpuppets on: March 25, 2013, 06:11:52 PM
Not a new idea.  In general, you need to provably attach some sort of cost associated with an identity.  That cost could be a monetary cost (bitcoins or dollars), a proof of work, or something else.

665  Bitcoin / Hardware / Re: Avalon ASIC users thread on: March 25, 2013, 03:34:37 PM

Here is a thread describing my bitcoind + eloipool solo mining configuration.

This is also the configuration you would use for a mining farm.

666  Bitcoin / Hardware / Re: Avalon users: bitcoind + eloipool configuration on: March 25, 2013, 03:25:37 PM
Reserved.
667  Bitcoin / Hardware / Avalon users: bitcoind + eloipool configuration on: March 25, 2013, 03:20:38 PM
Here is the simple solo mining and mining farm configuration used here.  At current difficulty, ignoring variance, an Avalon should, on average, generate a block every...

Quote
The average time to generate a block at 68000.0 Mhps, given difficulty of 6695826.2826, is 4 days, 21 hours, 28 minutes, and 43 seconds

Pool is probably preferable to most, as you might have incredibly bad luck and not generate a block for a couple weeks.  In any case, here is the bitcoind + eloipool configuration on Linux.

If you like these instructions, there is a donation address in the sig.




bitcoind setup

1) Obtain a compiled bitcoind somehow.  Compiling your own is outside the scope of these instructions.  I'm told there is an Ubuntu PPA somewhere.

2) Decide on a data directory location.  It must be on a fast hard drive, preferably SSD, and have at least 10GB of free space.

3) In this directory, create bitcoin.conf text file, with the following contents:

Code:
rpcuser=MY_RPC_USERNAME
rpcpassword=MY_RPC_PASSWORD
logtimestamps=1

Obviously, change the MY_RPC_xxx to a username and password.

4) Create a newblock.sh script, with the following contents:

Code:
#!/bin/sh

killall -USR1 eloipool.py

Mark it executeable via "chmod 0755 newblock.sh"

5) Create a run-bitcoind.sh script, with the following contents:

Code:
#!/bin/sh

/spare/repo/bitcoin/src/bitcoind \
-datadir=/spare/bitcoin/data -daemon \
-blocknotify=/garz/repo/eloipool/newblock.sh

Mark it executeable via "chmod 0755 run-bitcoind.sh"

You must modify the (a) bitcoind path, (b) -datadir path, and (c) -blocknotify path to fit your local computer.

6) Run bitcoind via the run-bitcoind.sh script.  Watch debug.log in the data directory, to make sure it started the Initial Block Download (bitcoin network sync).  This might take a few hours, to download all the blocks.  If you are technically minded and motivated, you may download the blockchain torrent to give this process a jump-start.



eloipool setup

1) Download eloipool dependencies, either from your Linux packager, or directly:

Python 3                        http://python.org
python-bitcoinrpc       https://github.com/jgarzik/python-bitcoinrpc
python-base58           https://gitorious.org/bitcoin/python-base58
midstate                        http://gitorious.org/midstate/midstate

2) For python-bitcoinrpc, check out an older release,

Code:
$ cd /repo/python-bitcoinrpc
$ git checkout -b solo-mining 770881c8bd9b1f92427290270b37a28751cf9df0

3) Check out eloipool,

Code:
$ git clone git://gitorious.org/bitcoin/eloipool.git

4) Copy config.py.example to config.py, and make the following several edits,

a) change ServerName to something unique

b) increase share target (note increased '0' and decreased 'f'):
Code:
-ShareTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
+ShareTarget = 0x000000000fffffffffffffffffffffffffffffffffffffffffffffffffffffff

c) DynamicTargetting = 2

d) DynamicTargetGoal = 6

e) change TrackerAddr to YOUR bitcoin address

f) comment out CoinbaserCmd,

Code:
-CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'
+#CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'

g) update TemplateSources to point to your local bitcoind RPC, including chosen username/password, and comment out the secondary source:

Code:
@@ -57,41 +57,41 @@
 TemplateSources = (
        {
                'name': 'primary',
-               'uri': 'http://user:pass@localhost:8332',
+               'uri': 'http://MY_RPC_USERNAME:MY_RPC_PASSWORD@127.0.0.1:8332',
                'priority': 0,
                'weight': 1,
        },
-       {
-               'name': 'secondary',
-               'uri': 'http://user:pass@localhost:18332',
-               'priority': 1,
-               'weight': 1,
-       },
+#      {
+#              'name': 'secondary',
+#              'uri': 'http://user:pass@localhost:18332',
+#              'priority': 1,
+#              'weight': 1,
+#      },
 )

g) empty TemplateChecks (or comment out 100%),

Code:
 TemplateChecks = (
 )

h) comment out or delete BlockSubmissions

i) change log settings, and switch from testnet3 mining to mainnet:

Code:
-DelayLogForUpstream = False
+DelayLogForUpstream = True
 
 # Bitcoin p2p server for announcing blocks found
-UpstreamBitcoindNode = ('127.0.0.1', 18333)  # testnet
+UpstreamBitcoindNode = ('127.0.0.1', 8333)
 
 # Network ID for the primary blockchain
 # Other known network IDs can be found at:
 #     https://en.bitcoin.it/wiki/Protocol_specification#Message_structure
-UpstreamNetworkId = b'\xFA\xBF\xB5\xDA'  # testnet
+UpstreamNetworkId = b'\xF9\xBE\xB4\xD9'

j) disable transaction-related bug workaround:

Code:
-POT = 2
+#POT = 2

k) update ShareLogging to reflect your desires.  The simplest is to delete all the SQL-related entries, leaving only the textfile logfile.  With solo mining, you don't care so much about shares.

Code:
ShareLogging = (
        {
                'type': 'logfile',
                'filename': 'share-logfile',
                'format': "{time} {Q(remoteHost)} {username} {YN(not(rejectReason))} {dash(YN(upstreamResult))} {dash(rejectReason)} {solution}\n",
        },
)

l) change log filename to something useful,

Code:
 LogFile = {
-       'filename': 'filename.log',
+       'filename': 'eloipool.log',

m) Create a runit.sh script for eloipool, with the contents,

Code:
#!/bin/sh

PYTHONPATH=/spare/repo/python-bitcoinrpc:/garz/repo/python-base58:/garz/repo/midstate \
     nohup ./eloipool.py 2>&1 >/dev/null &

You must change the paths to suit your local system.

n) Run eloipool with runit.sh script

o) Let's assume you are running the pool software on 192.168.1.40 IP address.  Set up your miner configuration like this:

Pool X: stratum+tcp://192.168.1.40:3334
Pool X username: 1NqqjQWXDLAoNycAS2ZryueuhNLJtcjvGy
Pool X password: x

668  Bitcoin / Hardware / Re: Who ordered batch #3 Avalon ? on: March 25, 2013, 02:52:13 PM
Ordered one 3-module unit.
669  Bitcoin / Mining / Re: block.version=1 blocks will all be orphaned soon on: March 25, 2013, 02:23:02 PM
What happens to the few coinbase transactions with duplicate transaction id? Are the coins irrecoverably lost?

Yes.  The newer coinbase stomps the older coinbase, making the older coinbase unspendable.

670  Bitcoin / Bitcoin Discussion / Re: Upcoming network event: block v2 lock-in on: March 25, 2013, 07:35:28 AM
This event is now past.
671  Bitcoin / Mining / Re: block.version=1 blocks will all be orphaned soon on: March 25, 2013, 07:35:08 AM
This event is now past.
672  Bitcoin / Project Development / Re: [ANNOUNCE] Bitmessage - P2P Messaging system based partially on Bitcoin on: March 25, 2013, 03:24:55 AM
Peer address issue...

Code:
Trying an outgoing connection to 10.10.10.1 : 8444
[...]
Could NOT connect to 10.10.10.1 during outgoing attempt. timed out

The code should not be distributing and connecting to peer addresses for internal / site-specific / unrouted addresses.

673  Bitcoin / Press / Re: 2013-03-21 National Journal "How Washington Plans to Regulate Your Bitcoins" on: March 24, 2013, 09:05:46 PM
Fixed thread title to read "National Journal" (as opposed to "National Review")
674  Other / Beginners & Help / Re: I am a certified Anti-Money Laundering agent. (AMLCA) on: March 24, 2013, 02:15:48 AM
BTW, Jeff...You are always welcome to any information from me free of charge on here or any other way. (And that goes for any of the other Bitcoin devs) Just happy to know you. Contact me anytime. You guys are the front lines of a very important work.

PM sent Smiley

675  Bitcoin / Bitcoin Discussion / Re: Press center on the website - looking for volunteers on: March 23, 2013, 11:29:38 PM
There is a really strong reason why all large corporations have a dedicated team of PR staff, and it's because helping journalists write good stories is a full time job...Bitcoin does not have any dedicated PR people, nor should it.

Why shouldn't Bitcoin be promoted using PR resources like any other product?

"Any other product" tends to imply a conventional company with conventional PR resources, not an open source invention.

676  Bitcoin / Bitcoin Discussion / Re: Upcoming network event: block v2 lock-in on: March 23, 2013, 05:25:12 PM
One of the devs should really speak to deepbit.

Deepbit has already upgraded.  That's one of the reasons this network event is approaching sooner rather than later.

677  Bitcoin / Bitcoin Discussion / Re: Press center on the website - looking for volunteers on: March 23, 2013, 04:23:51 PM

Definitely would love to have an open, distributed bitcoin PR team.

Please keep me in the loop.

678  Bitcoin / Bitcoin Discussion / Upcoming network event: block v2 lock-in on: March 23, 2013, 04:16:12 PM
Reminder:

Once a supermajority (95%) of mining reaches block version 2, version 1 blocks will be rejected.  Effectively, this is a network-wide upgrade.  This event seems likely to occur in the next week.

Version 2 block specification: https://en.bitcoin.it/wiki/BIP_0034
bitcoind 0.7.2 was the first to support block v2.

Watching for the event: http://blockorigin.pfoe.be/top.php  The text is at the bottom:
"We are currently at 100 out of the latest 1000 blocks on version 1 (10.00%) and 899 out of the latest 1000 blocks on version 2 (89.90%)"

Users should not be impacted.  Some ancient miners will produce newly-invalid blocks (v1), that will get ignored.  The easy solution is to mine using a recent bitcoind (0.8.1 or later ideally).  If you are a miner and need help upgrading to v2, ping us on #bitcoin-dev or bitcoin-development@lists.sourceforge.net.

Particular impact might be felt in the merged-mining and 'getwork' mining communities, because they are most likely to be running ancient software that is difficult to upgrade.

679  Bitcoin / Development & Technical Discussion / A bitcoin UDP P2P protocol extension on: March 23, 2013, 07:16:52 AM
Here is a rough draft implementation of a UDP P2P protocol extension
for bitcoin:

     https://github.com/jgarzik/bitcoin/tree/udp
     http://yyz.us/bitcoin/udp-v0.patch

Protocol specification (such that it is):

- UDP, bound to same port as TCP P2P (normally 8333)
- Active, simultaneous TCP P2P connection required (useful against DoS and other attacks)
- Same message format as TCP P2P, same pchMessageStart conventions, etc. (my CNetMessage pull req would be helpful here)
- Multiple P2P messages per UDP packet permitted
- Max UDP packet size 100*1024 bytes
- Advertises NODE_UDP in nServices
- New "getudpcook" TCP P2P command returns a "udpcook" message, containing a yummy cookie
- UDP P2P commands "inv", "tx" and "addr" are handled as if received via TCP
- UDP P2P command "udpsub" sets a mask, that subscribes to one or more data broadcasts.
- When USM_INV_BCAST mask bit is set, receive "inv" messages via UDP rather than TCP.

Project and design goals (or, why do this?):

- It is theorized that UDP may be useful for some messages we broadcast throughout the network
- A productive discussion STARTS with code, otherwise discussion continues forever.
- Investigate improving "inv" relay speed
- Investigate unconditional "tx" broadcasting via UDP, as "inv" alternative, for small tx's.
- Investigate improving block relay speed (or perhaps block header relay speed)
- Open up new design avenues, for P2P patterns more suited to UDP than TCP in general.

It must be emphasize that this is supposed to be a starting point, not a set-in-stone requirement that This Is How The Protocol Must Look.  I don't think we will know how the UDP protocol should look until after testing and experimentation, or even if it is a good idea at all.

680  Economy / Goods / Re: [WTS] HUGE tracts of land! OK, 3.3 acres at least. on: March 22, 2013, 08:19:17 PM

For the purposes of property tax calculation, these are the assessed values, according to Wake County:

Lot #5: $67,146 (paid $412 for property taxes in current tax year)
Lot #11: $58,900 (paid $361 for property taxes in current tax year)

The tax values are above listing price, and in my opinion, are over-valued.  The property values are re-assessed every few years, but you can always go through a months-long appeals process to "short circuit" that.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 [34] 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 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 ... 162 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!