Bitcoin Forum
May 11, 2024, 09:32:55 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 »
181  Bitcoin / Hardware / Re: Ultra-Low-Cost DIY FPGA Miner - 175MH/s @ $1/MH on: September 22, 2011, 07:20:38 AM
... You need to build a 1.2V 5+A PSU and thats not easy and cheap. ...
Pretty easy if you use COTS DC/DC converter modules.
YV09T60 + input/output caps + 2kR 1% resistor = 12V->1.2V 60A, Vccint for 6 to 8 LX150.
For Vccaux and Vccio a small 12V or 5V->2.5V DC/DC, 3A is plenty for 8 LX150+controller if you only have JTAG and 100MHz SPI.
If you also need a few dozen mA @ 3.3V (for example for a USB transceiver), LDO from 5V or just grab it from the ATX psu.
Trivial to design+build on a 2-layer PCB or even protoboard.
182  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 21, 2011, 01:57:41 PM
Create your datadir. Make sure it's empty. put Geist's config there. Start geist with -datadir="path_to_datadir"

Do not pass port as startup option - config should be taking care of that.

If you did everything right, it will creater a testnet folder in the datadir which you specified and connect to channel #geistgeld00

It doesn't seem to:

~$ ggd -datadir=.gg/
Bitcoin: Unable to bind to port 8333 on this computer.  Bitcoin is probably already running.

That's why I also try seting the port on the command line.
use the full path to datadir
183  Bitcoin / Mining software (miners) / Re: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards on: September 20, 2011, 09:59:47 PM
I'll give you a big fat hint: maybe having a nice and regular structure for the W updates isn't the best option...
184  Bitcoin / Hardware / Re: Ultra-Low-Cost DIY FPGA Miner - 175MH/s @ $1/MH on: September 20, 2011, 09:57:16 PM
Some of you guys have a reading comprehension problem?
The LX25 is just for testing a new layout and reflow process. If it doesn't work it was cheaper than a LX150. If it does work you get a LX25 on a nice 0.1" breakout board.
And yea, at low qty and without assembly $175 for LX150+discretes+board looks pretty much right.
Also, LOL @ that toy heatsink. a 25*25*15 is barely enough, better to use a 30*30*20 or even a 40*40 if there's space for it. and you'll still need quite a bit of airflow.
185  Bitcoin / Wallet software / Re: Merkle Tree example on: September 19, 2011, 09:06:35 PM
"You're doing it wrong"
note that the byte order for displaying these hashes is basically exactly backwards vs. normal notation
I'm using hex strings without quotes to show bytes-as-they-would-be-in-memory and in quotes to show uint256s in hex like in blockexplorer or returned by bitcoin rpc

tx hashes for that block:
"3a459eab5f0cf8394a21e04d2ed3b2beeaa59795912e20b9c680e9db74dfb18c"
"be38f46f0eccba72416aed715851fd07b881ffb7928b7622847314588e06a6b7"
"d173f2a12b6ff63a77d9fe7bbb590bdb02b826d07739f90ebb016dc9297332be"
"59d1e83e5268bbb491234ff23cbbf2a7c0aa87df553484afee9e82385fc7052f"
"f1ce77a69d06efb79e3b08a0ff441fa3b1deaf71b358df55244d56dd797ac60c"
"84053cba91fe659fd3afa1bf2fd0e3746b99215b50cd74e44bda507d8edf52e0"
again, that's when you read them as uint256s, little-endian all the way, so "bytes in memory" those really are:
8cb1df74dbe980c6b9202e919597a5eabeb2d32e4de0214a39f80c5fab9e453a
b7a6068e5814738422768b92b7ff81b807fd515871ed6a4172bacc0e6ff438be
...
so, to start the merkle building, we do sha256(sha256(h1 . h2)) for the first two
result:
2dd3ce205cf8d03f773d46d24becfd72c766deaa0d1327d7e4c810265f59a313
again read it backwards because we display stuff in little-endian, and...
"13a3595f2610c8e4d727130daade66c772fdec4bd2463d773fd0f85c20ced32d"
looks familiar?
do the same for "d173..." and "59d1..." and...
"f6ae335dc2d2aecb6a255ebd03caaf6820e6c0534531051066810080e0d822c8"
last pair...
"a751efbeabe73bdf9d08df5760104feff915d9d807d4c62178cdeb98d8c25f43"

now we only have 3, so last one gets concat'd with itself
"13a3595f2610c8e4d727130daade66c772fdec4bd2463d773fd0f85c20ced32d"
"f6ae335dc2d2aecb6a255ebd03caaf6820e6c0534531051066810080e0d822c8"
gives
"59545fd8dfdd821ca7accecab0655d77437f5bba5aaa5ea8c042a26bc9ae514b"

"a751efbeabe73bdf9d08df5760104feff915d9d807d4c62178cdeb98d8c25f43"
"a751efbeabe73bdf9d08df5760104feff915d9d807d4c62178cdeb98d8c25f43"
gives
"15eca0aa3e2cc2b9b4fbe0629f1dda87f329500fcdcd6ef546d163211266b3b3"

and final level of the tree
"59545fd8dfdd821ca7accecab0655d77437f5bba5aaa5ea8c042a26bc9ae514b"
"15eca0aa3e2cc2b9b4fbe0629f1dda87f329500fcdcd6ef546d163211266b3b3"
gives
"9cdf7722eb64015731ba9794e32bdefd9cf69b42456d31f5e59aedb68c57ed52"
186  Bitcoin / Mining software (miners) / Re: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards on: September 19, 2011, 05:53:31 PM
Yep, and that's with 200ps clock jitter, your assumed 0-jitter clock would knock it down to 5.091ns cycle time => a bit over 196MHz Grin
On my real world rev1.1 boards with -2 speed grade, 1230-1250mV Vccint and 25°C ambient, this bitstream averages 193.9 MHz at very low error rate (0 errors over 2**35 hashes).
Pushing up error rate to 0.1% => 198.3MHz average.
187  Bitcoin / Mining software (miners) / Re: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards on: September 18, 2011, 09:48:35 AM
And here the exact same HDL/settings but using ISE 13.2 and tightening timing a bit:

Total REAL time to MAP completion:  30 mins 17 secs
Total CPU time to MAP completion:   28 mins 23 secs

Slice Logic Utilization:
  Number of Slice Registers:                92,968 out of 184,304   50%
    Number used as Flip Flops:              92,823
    Number used as Latches:                      0
    Number used as Latch-thrus:                  0
    Number used as AND/OR logics:              145
  Number of Slice LUTs:                     60,406 out of  92,152   65%
    Number used as logic:                   34,257 out of  92,152   37%
      Number using O6 output only:          21,087
      Number using O5 output only:             409
      Number using O5 and O6:               12,761
      Number used as ROM:                        0
    Number used as Memory:                   2,721 out of  21,680   12%
      Number used as Dual Port RAM:              0
      Number used as Single Port RAM:            0
      Number used as Shift Register:         2,721
        Number using O6 output only:           450
        Number using O5 output only:             0
        Number using O5 and O6:              2,271
    Number used exclusively as route-thrus: 23,428
      Number with same-slice register load: 23,414
      Number with same-slice carry load:        14
      Number with other load:                    0

Slice Logic Distribution:
  Number of occupied Slices:                15,446 out of  23,038   67%
  Number of LUT Flip Flop pairs used:       60,460
    Number with an unused Flip Flop:           868 out of  60,460    1%
    Number with an unused LUT:                  54 out of  60,460    1%
    Number of fully used LUT-FF pairs:      59,538 out of  60,460   98%
    Number of slice register sites lost
      to control set restrictions:               0 out of 184,304    0%

Total REAL time to Router completion: 25 mins 23 secs
Total CPU time to Router completion: 24 mins 26 secs


----------------------------------------------------------------------------------------------------------
  Constraint                                |    Check    | Worst Case |  Best Case | Timing |   Timing   
                                            |             |    Slack   | Achievable | Errors |    Score   
----------------------------------------------------------------------------------------------------------
  TS_coreclk = PERIOD TIMEGRP "tncoreclk" 1 | SETUP       |     0.233ns|     5.172ns|       0|           0
  85 MHz HIGH 50% INPUT_JITTER 0.2 ns       | HOLD        |     0.316ns|            |       0|           0
188  Bitcoin / Mining software (miners) / Re: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards on: September 18, 2011, 09:19:54 AM
As a little encouragement, here's a decent run for my old design (ISE synth+map+p&r, letting synth infer shift regs, no placement constraints, ...) for -3 speed grade

Device Utilization Summary:

Slice Logic Utilization:
  Number of Slice Registers:                92,964 out of 184,304   50%
    Number used as Flip Flops:              92,819
    Number used as Latches:                      0
    Number used as Latch-thrus:                  0
    Number used as AND/OR logics:              145
  Number of Slice LUTs:                     62,141 out of  92,152   67%
    Number used as logic:                   34,288 out of  92,152   37%
      Number using O6 output only:          21,087
      Number using O5 output only:             424
      Number using O5 and O6:               12,777
      Number used as ROM:                        0
    Number used as Memory:                   2,721 out of  21,680   12%
      Number used as Dual Port RAM:              0
      Number used as Single Port RAM:            0
      Number used as Shift Register:         2,721
        Number using O6 output only:           450
        Number using O5 output only:             0
        Number using O5 and O6:              2,271
    Number used exclusively as route-thrus: 25,132
      Number with same-slice register load: 25,117
      Number with same-slice carry load:        15
      Number with other load:                    0

Slice Logic Distribution:
  Number of occupied Slices:                16,519 out of  23,038   71%
  Number of LUT Flip Flop pairs used:       62,163
    Number with an unused Flip Flop:         2,573 out of  62,163    4%
    Number with an unused LUT:                  22 out of  62,163    1%
    Number of fully used LUT-FF pairs:      59,568 out of  62,163   95%
    Number of slice register sites lost
      to control set restrictions:               0 out of 184,304    0%

...
Total REAL time to PAR completion: 19 mins 45 secs
Total CPU time to PAR completion: 20 mins 34 secs


Timing:
 ================================================================================
 Timing constraint: TS_coreclk = PERIOD TIMEGRP "tncoreclk" 182 MHz HIGH 50% INPUT_JITTER 0.2 ns;
  3102658 paths analyzed, 386321 endpoints analyzed, 0 failing endpoints
  0 timing errors detected. (0 setup errors, 0 hold errors, 0 component switching limit errors)
  Minimum period is   5.262ns.
 --------------------------------------------------------------------------------
 
 Paths for end point XLXI_A/rb20/regt1_31 (SLICE_X104Y33.CIN), 252 paths
 --------------------------------------------------------------------------------
 Slack (setup path):     0.232ns (requirement - (data path - clock path skew + uncertainty))
   Source:               XLXI_A/rb19/outE_17 (FF)
   Destination:          XLXI_A/rb20/regt1_31 (FF)
   Requirement:          5.494ns
   Data Path Delay:      4.928ns (Levels of Logic = Cool
   Clock Path Skew:      -0.111ns (0.620 - 0.731)
   Source Clock:         coreclk rising at 0.000ns
   Destination Clock:    coreclk rising at 5.494ns
   Clock Uncertainty:    0.223ns
 
   Clock Uncertainty:          0.223ns  ((TSJ^2 + TIJ^2)^1/2 + DJ) / 2 + PE
     Total System Jitter (TSJ):  0.070ns
     Total Input Jitter (TIJ):   0.200ns
     Discrete Jitter (DJ):       0.233ns
     Phase Error (PE):           0.000ns
 
   Maximum Data Path at Slow Process Corner: XLXI_A/rb19/outE_17 to XLXI_A/rb20/regt1_31
     Location             Delay type         Delay(ns)  Physical Resource
                                                        Logical Resource(s)
     -------------------------------------------------  -------------------
     SLICE_X126Y28.BQ     Tcko                  0.408   XLXI_A/rb19/outE<19>
                                                        XLXI_A/rb19/outE_17
     SLICE_X115Y27.A4     net (fanout=8)        1.658   XLXI_A/rb19/outE<17>
     SLICE_X115Y27.A      Tilo                  0.259   XLXI_A/rb20/s1<6>
                                                        XLXI_A/rb20/s1<6>1
     SLICE_X104Y27.CX     net (fanout=1)        1.798   XLXI_A/rb20/s1<6>
     SLICE_X104Y27.COUT   Tcxcy                 0.093   XLXI_A/rb20/regt1<7>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<7>
     SLICE_X104Y28.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<7>
     SLICE_X104Y28.COUT   Tbyp                  0.076   XLXI_A/rb20/regt1<11>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<11>
     SLICE_X104Y29.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<11>
     SLICE_X104Y29.COUT   Tbyp                  0.076   XLXI_A/rb20/regt1<15>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<15>
     SLICE_X104Y30.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<15>
     SLICE_X104Y30.COUT   Tbyp                  0.076   XLXI_A/rb20/regt1<19>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<19>
     SLICE_X104Y31.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<19>
     SLICE_X104Y31.COUT   Tbyp                  0.076   XLXI_A/rb20/regt1<23>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<23>
     SLICE_X104Y32.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<23>
     SLICE_X104Y32.COUT   Tbyp                  0.076   XLXI_A/rb20/regt1<27>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<27>
     SLICE_X104Y33.CIN    net (fanout=1)        0.003   XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_cy<27>
     SLICE_X104Y33.CLK    Tcinck                0.314   XLXI_A/rb20/regt1<31>
                                                        XLXI_A/rb20/Madd_s1[31]_ch[31]_add_18_OUT_xor<31>
                                                        XLXI_A/rb20/regt1_31
     -------------------------------------------------  ---------------------------
     Total                                      4.928ns (1.454ns logic, 3.474ns route)
                                                        (29.5% logic, 70.5% route)
189  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 18, 2011, 08:40:12 AM
hmm, the "peers disagree with NTP" looks more and more like it can pretty much only be a bad ntp response:

Added time data, samples 17, offset -2 (+0 minutes)
-2  -2  -2  -1  -1  -1  -1  -1  -1  -1  -1  -1  +0  +0  +0  +0  +0  |  nTimeOffset = -1  (+0 minutes)

This is on a box with ntpd synced to a local stratum1 where the current SNTP code consistently gets < 10ms offset to local time from all pool.ntp.org servers I tried.

The basic problem is... we can't trust the local clock to be accurate, and if median-of-peers and SNTP disagree by more than a few sec... which one is right?
Gut feeling says if peers and NTP disagree by too much preferring median-of-peers time and issuing a warning might be better, current code uses NTP time and issues a warning under those conditions.
190  Bitcoin / Mining / Re: FPGA Miner Design for Sale to Someone willing to Market It on: September 17, 2011, 07:42:39 PM
Yup, 750Mh/s on a 240 is pretty easy. On a 195... tight. on a 130 or 75? Doubt it.
191  Bitcoin / Mining / Re: FPGA Miner Design for Sale to Someone willing to Market It on: September 17, 2011, 12:06:32 PM
Piling on top of the "These guys are getting completely insane discounts from xilinx or this is BS" crowd.
192  Bitcoin / Development & Technical Discussion / Re: Please help test: bitcoin version 0.4 release candidate 2 on: September 17, 2011, 11:57:27 AM
Tested with Opera on linux here, all 4 cloudfront links give access denied.
links on https://github.com/bitcoin/bitcoin/downloads - same result.
Downloads from http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/test/ work...
193  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 14, 2011, 09:33:21 PM
the high reject rate is because cgminer is ignoring "target" in getwork and just blindly sends every H==0 share. so at diff 100 you'll see a 99% reject rate.
194  Alternate cryptocurrencies / Altcoin Discussion / Re: ARE YOU MINING GG? on: September 14, 2011, 12:51:28 AM
Yup. Throwing 9 Gh of legit hashrate at it as a little "you must be at least *this* tall to 51% this" barrier. Wink
195  Bitcoin / Development & Technical Discussion / Re: Does the constant generation of bitcoin addresses clutter the blockchain? on: September 14, 2011, 12:45:15 AM
I'm interested to hear of feasible side-channel attacks I neglected to consider,
Non-random random number generator.
Iirc the current implementation uses openssls default crypto RNG, so should be decently secure unless a debian maintainer comes by. *ducks*
196  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 13, 2011, 07:26:32 PM
Yeah, if your system clock is off more than 10 sec or so, you pretty much need ntp=1 (hrrrm... actually it should be gracefully falling back to median-of-peer-time in that case... wtf?)
197  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 13, 2011, 07:13:52 PM
block count would easily shed some light on this:
60k+ = you're on the old GG chain without enablefullretargetperiod
~350 = you're on the old GG chain with enablefullretargetperiod
~240 = you're on the new GG chain without enablefullretargetperiod
~1650 = you're on the new GG chain with enablefullretargetperiod

last one is the "real" chain.
198  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 13, 2011, 07:07:55 PM
I *think* this might be some people running without enablefullretargetperiod=1, but I'm far from certain on that.
199  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 13, 2011, 06:39:02 PM
Got a new card, now I'm at ~400 mh/s

Still can't get any work in.  Cards will chug away, but even after 10m still at 0/0.  Using poclbm, win7x64, 2.1sdk

I still think I may be doing something wrong... but I can't tell.  So my best guess is 400 is still too low.
    "blocks" : 1494,
    "difficulty" : 111.50074768,
= about 20min expected average at 400Mh/s
200  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANNOUNCE] New alternate cryptocurrency - Geist Geld on: September 13, 2011, 06:37:13 PM
That would explain things.  Have the Bitcoin devs fixed the timewarp (sorry for lack of a better description, that's the only word I could think of) issue and what's there to stop someone from doing it right now?  Or is there still a bit of muscle required to overcome the existing 10-12TH/s on the network?
1. No.
2. You still roughly need 51% to do it, so something like 15Th/s for bitcoin...
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!