Bitcoin Forum
May 08, 2024, 10:45:15 PM *
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 »
781  Economy / Speculation / Re: 10k Sell wall just now on: November 07, 2013, 12:53:26 AM
In all seriousness it very well might be, because there's little logical reasons to sell that much coins on mtgox right now... On an exchange where you can get your usd maybe, but not on mtgox...
782  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: November 07, 2013, 12:32:05 AM
ATH on Bitstamp 267.79 USD/BTC.
783  Bitcoin / Development & Technical Discussion / Re: For fun: the lowest block hash yet on: November 06, 2013, 10:58:52 PM
2013-10-27 14:55:42 SetBestChain: new best=000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050  height=266381  log2_work=73.237967  tx=26093998  date=2013-10-27 14:49:44 progress=0.999972

In [592]: math.log((2**256)/0x000000000000000000028c32e6952731326747bae4be8db0f832d6eea0362050,2)
Out[592]: 78.65083195521588


This basically mean that brute-forcing something of 78.65 bits (80 almost) is possible?
784  Bitcoin / Pools / Re: [100 TH] BitMinter.com [1% PPLNS,Pays TxFees + MergedMining,Stratum,GBT,vardiff] on: October 11, 2013, 01:13:18 PM
I solved a block, 256M, hell of a solve!
785  Bitcoin / Pools / Re: [90 TH] BitMinter.com [ASIC support: var diff, Stratum, GBT, rollntime] on: October 10, 2013, 08:57:19 PM
Hey Doc, please change the title of this Topic to

[100 TH] BitMinter.com [1% PPLNS; Pays TX FEES; ASIC support: Stratum, var diff, GBT; port 80, 3333, 5050]

Right now it's not very appealing to newcomers.
786  Bitcoin / Pools / Re: [90 TH] BitMinter.com [ASIC support: var diff, Stratum, GBT, rollntime] on: October 10, 2013, 11:01:31 AM
EvenMoreConfused1 broke the block table! Nice job picking long usernames
787  Bitcoin / Pools / Re: [80 TH] BitMinter.com [ASIC support: var diff, Stratum, GBT, rollntime] on: October 07, 2013, 11:06:12 PM
But still not solving this 11h+ block.
788  Bitcoin / Pools / Re: [80 TH] BitMinter.com [ASIC support: var diff, Stratum, GBT, rollntime] on: October 07, 2013, 10:59:00 PM
We are at 100 TH/s now.
789  Bitcoin / Pools / Re: [45 TH/s] BitMinter.com [ASIC support: var diff, Stratum, GBT, rollntime] on: September 30, 2013, 12:40:49 AM
intermittent disconnect & reconnect, anyone else?
790  Bitcoin / Mining software (miners) / Re: BFGMiner 3.2.1: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, BE Blade on: September 24, 2013, 05:32:08 PM
I need to get the firmware version of a Single SC, how to get the full dump of GetInfo in bfgminer (like in cgminer with tcp socket 'stats'),
I tried 'devdetails' or 'devdetail' (both won't work at all), and 'devs' doesn't return the fw version.
791  Bitcoin / Hardware / Re: Experimenting with Jalapeno firmware... on: September 24, 2013, 10:37:20 AM
Hello everyone, could a good spirit point me to the tools/software I need to flash a Single SC?
792  Bitcoin / Mining software (miners) / Re: [ANN] Eloipool - FAST Python3 pool server software - GBT/stratum/dyntarget/proxy on: August 08, 2013, 05:50:18 PM
Or do I have to somehow calculate it with the accepted shares logged?
793  Bitcoin / Mining / Re: Generate fake hashrate to test client & server resources on: August 08, 2013, 04:43:04 PM
So if a mining-server is linked to a bitcoind having a network difficulty of 1, the mining-client will send way more share and the mining-server accepting way more. But is it possible to say generate 1 TH/s of fake share and get them to accept by the server, without having to fiddle with the mining-server source code too much.

I wonder how it was done when testing PoolServerJ performance compared to pushpool: http://web.archive.org/web/20111129134439/http://poolserverj.org/performance-testing/
794  Bitcoin / Mining software (miners) / Re: [ANN] Eloipool - FAST Python3 pool server software - GBT/stratum/dyntarget/proxy on: August 08, 2013, 04:25:00 PM
How to estimate the current hashrate of the pool? Is already some stats somewhere?
795  Bitcoin / Mining / Generate fake hashrate to test client & server resources on: August 08, 2013, 02:42:42 PM
In a controlled environment on both side (mining-client & mining-server), how can one generate fake hashrate on the client side, get it accepted by the server as valid to generate fake bitcoins, so one could test the hardware resources of the server (and the client as well).
796  Bitcoin / Mining software (miners) / Re: [ANN] Eloipool - FAST Python3 pool server software - GBT/stratum/dyntarget/proxy on: August 08, 2013, 03:56:02 AM
Fixed, had to checkout at commit 770881c8bd9b1f92427290270b37a28751cf9df0 of python-bitcoinrpc.
Is there a way to have the python-bitcoinrpc git updated to the latest commit and still get it to work with eloipool?
797  Bitcoin / Mining software (miners) / Re: [ANN] Eloipool - FAST Python3 pool server software - GBT/stratum/dyntarget/proxy on: August 07, 2013, 09:38:38 PM
What I run:
Code:
root@server:~/pool/# ./bitcoind &
root@server:~/pool/# python3 eloipool.py

I'm getting an infinite loop error! The message doesn't stop and blocks the terminal...

Code:
Traceback (most recent call last):
  File "/root/pool/merklemaker.py", line 692, in run
    self.merkleMaker_I()
  File "/root/pool/merklemaker.py", line 682, in merkleMaker_I
    self.merkleMaker_II()
  File "/root/pool/merklemaker.py", line 648, in merkleMaker_II
    return self._updateMerkleTree()
  File "/root/pool/merklemaker.py", line 548, in _updateMerkleTree
    self._updateMerkleTree_I()
  File "/root/pool/merklemaker.py", line 512, in _updateMerkleTree_I
    r = self._updateMerkleTree_fromTS(TS)
  File "/root/pool/merklemaker.py", line 477, in _updateMerkleTree_fromTS
    MP = self._CallGBT(TS)
  File "/root/pool/merklemaker.py", line 327, in _CallGBT
    MP = access.getblocktemplate(self.GBTReq)
  File "/root/pool/bitcoinrpc/authproxy.py", line 106, in __call__
    response = self._get_response()
  File "/root/pool/bitcoinrpc/authproxy.py", line 132, in _get_response
    parse_float=decimal.Decimal)
  File "/usr/lib/python3.2/json/__init__.py", line 322, in loads
    return cls(**kw).decode(s)
  File "/usr/lib/python3.2/json/decoder.py", line 353, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.2/json/decoder.py", line 371, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

2013-08-07 22:57:02,726 merkleMaker     CRITICAL        Traceback (most recent call last):
  File "/usr/lib/python3.2/json/decoder.py", line 369, in raw_decode
    obj, end = self.scan_once(s, idx)
StopIteration

During handling of the above exception, another exception occurred:

And the message repeats...

bitcoind config:
Code:
rpcuser=y
rpcpassword=x
maxconnections=256
daemon=1

eloipool config.py
Code:
# Please note that config files are Python source code!
# A common mistake is to put an option list (such as TemplateChecks,
# JSONRPCAddresses, etc) excluding the final comma.
# For example (this is WRONG):
#     JSONRPCAddresses = (
#         ('', 8337)  # <-- there must be a comma after EVERY item, even last
#     )
# Without the final comma, should the option list ever have only one item in
# it, Python would interpret the "main" parenthesis as a mere sub-expression
# instead of a list of values. If that occurs, you might get crazy errors, or
# things might just not work correctly. Be careful to not miss the commas.

### Settings relating to server identity

# Name of the server
ServerName = 'Private Pool'

### Settings relating to server scaling/load

# Share hashes must be below this to be valid shares
# If dynamic targetting is enabled, this is a minimum
ShareTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

# Automatically adjust targets per username
# 0 = disabled
# 1 = arbitrary targets
# 2 = power of two difficulties (zero bit counts)
DynamicTargetting = 2

# How many shares per minute to try to achieve on average
DynamicTargetGoal = 8

# Number of seconds hashrate is measured over
DynamicTargetWindow = 120

# Minimum and maximum of merkle roots to keep queued
WorkQueueSizeRegular = (0x100, 0x1000)

# Minimum and maximum of BLANK merkle roots to keep queued
# (used if we run out of populated ones)
WorkQueueSizeClear = (0x1000, 0x2000)

# Minimum and maximum of BLANK merkle roots to keep queued, one height up
# (used for longpolls)
WorkQueueSizeLongpoll = (0x1000, 0x2000)

# How long to wait between getmemorypool updates normally
MinimumTxnUpdateWait = 5

# How long to wait between retries if getmemorypool fails
TxnUpdateRetryWait = 1

# How long to sleep in idle loops (temporary!)
IdleSleepTime = 0.1

### Settings relating to reward generation

# Address to generate rewards to
TrackerAddr = '1BVi5pCdE5c37JDiF5tSur9vX1qB8xBLp9'

# Coinbaser command to control reward delegation
# %d is replaced with the total value of the block reward (in satoshis)
# %p is replaced with the previous block hash in hexadecimal
# NOTE: This example donates 1% of block rewards to Luke-Jr for Eloipool development
#CoinbaserCmd = 'echo -e "1\\n$((%d / 100))\\n1579aXhdwvKZEMrAKoCZhzGuqMa8EonuXU"'

### Settings relating to upstream data providers

# JSON-RPC servers to get block templates from
# See https://en.bitcoin.it/wiki/BIP_0023#Logical_Services for key details
TemplateSources = (
{
'name': 'primary',
'uri': 'http://y:x@localhost:8332',
'priority': 0,
'weight': 1,
},
# {
# 'name': 'secondary',
# 'uri': 'http://user:pass@localhost:18332',
# 'priority': 1,
# 'weight': 1,
# },
)

# JSON-RPC servers to check block proposals with
# If none provided, and selected source supports proposals, it alone will also
# be used for checking
# NOTE: Any servers listed here MUST support BIP 23 Block Proposals
# NOTE: Mainline bitcoind (as of 0.8) does NOT support this (though the 0.8.0.eligius branch does)
#TemplateChecks = (
# {
# 'name': 'primary',
# 'uri': 'http://user:pass@localhost:8332',
#
# # If 'unanimous' is true, no template will be used if this node
# # rejects it
# 'unanimous': False,
#
# # If check servers disagree on all templates, they will be scored and
# # the highest score will be used; 'weight' can be used to control the
# # scoring per-server
# 'weight': 1.1,
# },
# {
# 'name': 'secondary',
# 'uri': 'http://user:pass@localhost:18332',
# 'unanimous': False,
# 'weight': 1,
# },
#)

# JSON-RPC servers to submit found blocks to (when they meet the full target)
# The specific TemplateSource that the block was based on will always be sent
# the block first.
# If setting is not specified, or None, full TemplateSources list will be used.
# If an empty list, no extra submissions will be attempted.
# If an empty list, and the block was found on a "clear" merkle root (not based
# on any TemplateSource), the full TemplateSources list will be used.
#BlockSubmissions = (
# {
# 'name': 'primary',
# 'uri': 'http://user:pass@localhost:8332',
# },
# {
# 'name': 'secondary',
# 'uri': 'http://user:pass@localhost:18332',
# }
#)

# Templates will not be used unless they have an acceptance ratio above this
# Range: 0.00 - 1.00
MinimumTemplateAcceptanceRatio = 0

# No template with a combined total score below this will be used
MinimumTemplateScore = 1

# Set to True if you want shares meeting the upstream target to wait for a
# response from an upstream server before logging them. Otherwise, for such
# shares, upstreamResult will always be True and upstreamRejectReason will
# always be None. Note that enabling this may cause shares to be logged out of
# order, or with the wrong timestamp (if your share logger uses the log-time
# rather than share-time).
DelayLogForUpstream = False

# Bitcoin p2p server for announcing blocks found
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'\x0b\x11\x09\x07'  # testnet3
UpstreamNetworkId = b'\xF9\xBE\xB4\xD9'

# Secret username allowed to use setworkaux
#SecretUser = ""

# URI to send gotwork with info for every share submission
#GotWorkURI = ''

# Share hashes must be below this to be submitted to gotwork
GotWorkTarget = 0x00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff

# Aim to produce blocks with transaction counts that are a power of two
# This helps avoid any chance of someone abusing CVE-2012-2459 with them
# 1 = cut out feeless transactions; 2 = cut out even fee-included transactions (if possible)
#POT = 0

# Avoid mining feeless transactions except to satisfy POT
# Note this only works if POT is in fact enabled in the first place
Greedy = False

### Settings relating to network services
# Note that Eloipool only supports IPv6 sockets, and if you want to bind to an
# IPv4 address you will need to prepend it with ::ffff: eg ::ffff:192.168.1.2

# Addresses to listen on for JSON-RPC GBT/getwork server
JSONRPCAddresses = (
('', 8888),
)

# Addresses to listen on for Stratum mining server
StratumAddresses = (
('', 3334),
)

# Addresses to listen on for Bitcoin node
# Note this will only be used to distribute blocks the pool finds, nothing else
BitcoinNodeAddresses = (
('', 8338),
)

# Addresses that are allowed to "spoof" from address with the X-Forwarded-For header
TrustedForwarders = ('::ffff:127.0.0.1',)


# Logging of shares:
ShareLogging = (
{
'type': 'logfile',
'filename': 'share-logfile',
'format': "{time} {Q(remoteHost)} {username} {YN(not(rejectReason))} {dash(YN(upstreamResult))} {dash(rejectReason)} {solution}\n",
},
# {
# 'type': 'sql',
# 'engine': 'postgres',
# 'dbopts': {
# 'host': 'localhost',
# 'database': 'pooldb',
# 'user': 'eloipool',
# 'password': 'somethingsecret',
# },
# 'statement': "insert into shares (rem_host, username, our_result, upstream_result, reason, solution) values ({Q(remoteHost)}, {username}, {YN(not(rejectReason))}, {YN(upstreamResult)}, {rejectReason}, decode({solution}, 'hex'))",
# },
# {
# 'type': 'sql',
# 'engine': 'mysql',
# 'dbopts': {
# 'host': 'localhost',
# 'db': 'pooldb',
# 'user': 'eloipool',
# 'password': 'somethingsecret',
# },
# 'statement': "insert into shares (rem_host, username, our_result, upstream_result, reason, solution) values ({Q(remoteHost)}, {username}, {YN(not(rejectReason))}, {YN(upstreamResult)}, {rejectReason}, unhex({solution}))",
# },
{
'type': 'sql',
'engine': 'sqlite',
'dbopts': {
'database': 'share.db',
},
'statement': "insert into shares (remoteHost, username, rejectReason, upstreamResult, solution) values ({remoteHost}, {username}, {rejectReason}, {upstreamResult}, {solution})",
},
)

# Authentication
# There currently are 2 modules.
# - allowall will allow every username/password combination
# - simplefile will use the username/passwords from a file, which contains username<tab>password\n with no \n on the last line.
Authentication =  (
{
'module': 'allowall',
},
# {
# 'module': 'simplefile',
# 'filename': 'userdatabase',
# },
)

### Settings related to poolserver logging

# By default, significant events will be printed to the interactive console
# You can customize your logging using either simple parameters, or Python's advanced logging framework
# Note that using Python's logging framework will override the default console logging!

# To simply log everything to the system log (syslog) as well:
# LogToSysLog = True

# To make a log file:
# LogFile = 'filename.log'

# For a rotating log file:
LogFile = {
'filename': 'eloipool.log',
'when': 'midnight',
'backupCount': 7,
}
# For details, see:
# http://docs.python.org/3/library/logging.handlers.html#logging.handlers.TimedRotatingFileHandler
798  Bitcoin / Mining / Re: How mining pools break apart a work? on: August 06, 2013, 04:44:32 PM
Search for getmemorypool as well.
799  Bitcoin / Mining / Eloipool or stratum+stratum-mining? on: August 05, 2013, 11:18:26 PM
Hello,

I'm considering using one of these two software (eloipool or stratum+stratum-mining) to run a heavy stratum mining pool.

My basic concern is performance, which one is more scalable/efficient?

Also the second part of my inquiry is the overall support and resources available (i.e. how much work is needed to implement an Auto_add_user functionality similar to 50BTC) to work with the coinbase distribution and share logging.
800  Bitcoin / Development & Technical Discussion / Re: multi-signature transactions in javascript on: July 24, 2013, 11:41:27 AM
Hello,
Does any example of generating (from inputs + privates keys) a multi-signature transactions exist in any language? What about Javascript?

txtool is a command line tool written in JavaScript, that helps you build and sign multi-sig transactions.

https://bitcointalk.org/index.php?topic=249205.0
https://github.com/jgarzik/txtool


What if I don't have access to a bitcoind client? Do I have to reinvent the wheel?

Sure, bitcoinj makes this straight forward (from java):

https://code.google.com/p/bitcoinj/wiki/WorkingWithContracts

This looks like it's what I'm looking for, I have zero experience with java though.
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 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!