|
I'm interested in your GPUs.
|
|
|
|
So I can just add that as my, say, third dns server, and it'll resolve the addresses?
So I added it as my third name server, and it didn't work. It worked when I put it in the front of the list. Does this mean I'm using you for all my dns? I don't think I want that. I'm on Ubuntu, using NetworkManager you only use 1 dns server. all the other ones are "backups", in case if your primary one fails. |
|
|
|
Also, what is to stop a miner with the actual system from finding a full difficulty solution and modifying his miner to submit this result as a soloer. Wouldn't that kind of exploit be much more devastating and feasible?
I've thought of this exploit myself, but never really had the desire to try and implement it. This is definitely an exploit with the current system. I believe that currently, pools defend against this by sometimes sending a piece of work to their clients that they already know contains a winning hash. If they don't get it back, they will ban the client.
thanks for the detailed reply. i got one question though, what is preventing a miner in a pool from not reporting a "winning" block to the server? this could easily be implemented, with a connection to bitcoind. if the block is above the target, it is submitted to the server, if it's below the target, submit it to the client, and claim the block for itself. could this attack be feasible?
That is not feasible because the block that you are solving for the pool includes the transaction that pays the 50BTC to the pool's account, not yours. |
|
|
|
1. The block header will include 3 extra fields, which for now I'll call simply A, B and C.
2. B is a hash of A.
3. The block hash will be a hash of all the usual stuff and also B.
4. C is a hash of the concatenation of the block hash and A.
5. For the block to be valid: Instead of requiring that the block hash is less than (1 / (2^32 * difficulty)), it is required that the block
hash is less than (1 / 2^32) and C is less than (1 / difficulty).
So solo miners choose anything for A (maybe all zeros) and hash it once to find B. Then they calculate hashes normally but with B added. When they find a difficulty-1 hash they calculate C to extra check if it satisfies the real difficulty.
For pools, the operators choose A and keep it secret, but hand out B as part of the getwork. The participants can calculate the block hash and if it satisfies difficulty-1 they submit it as a share, but they don't know if it satisfies real difficulty because they don't know A and thus can't calculate C. The operator can of course make the verification, and at round end A is published as part of the block and participants can verify that none of their winning shares were rejected. Ok, I've reread this part. I like the idea but it doesn't seem to me there is a need to modify the protocol for the operator to produce B and send it over. Afaik, pool miners aren't directly part of the Bitcoin network, their connection and their work is with the pool only, so only that part could be modified. Also, what is to stop a miner with the actual system from finding a full difficulty solution and modifying his miner to submit this result as a soloer. Wouldn't that kind of exploit be much more devastating and feasible? the work that you receive from pools only works for pool. If you try to claim it, the reward will go to the pool owner, not you, because which address to pay to is embedded in the getwork from the pool. |
|
|
|
Cant compile version 0.8 JWasm v2.05, Mar 2 2011, Masm-compatible assembler.
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
jwasm(1) : Error A2209: Syntax error: ELF
jwasm(9) : Error A2209: Syntax error:
jwasm(10) : Error A2209: Syntax error:
jwasm(11) : Error A2209: Syntax error:
jwasm(14) : Error A2209: Syntax error: �4
jwasm(17) : Error A2209: Syntax error: e
jwasm(22) : Error A2209: Syntax error: 4
jwasm(24) : Error A2209: Syntax error:
jwasm(25) : Error A2209: Syntax error: (
jwasm(26) : Error A2209: Syntax error:
jwasm(27) : Error A2209: Syntax error:
jwasm(28) : Error A2209: Syntax error:
jwasm(31) : Error A2209: Syntax error: 4
jwasm(34) : Error A2209: Syntax error: 4
jwasm(38) : Error A2097: Backquote missing: `
jwasm(41) : Error A2097: Backquote missing: `
jwasm(44) : Error A2209: Syntax error:
jwasm(51) : Error A2209: Syntax error:
jwasm(55) : Error A2209: Syntax error:
jwasm(58) : Error A2209: Syntax error: �
jwasm(62) : Error A2209: Syntax error: ��
jwasm(63) : Error A2209: Syntax error: ��
jwasm(64) : Error A2209: Syntax error:
jwasm(68) : Error A2209: Syntax error:
jwasm(70) : Error A2209: Syntax error:
jwasm(74) : Error A2209: Syntax error: �
jwasm(76) : Error A2097: Backquote missing: `
jwasm(80) : Error A2209: Syntax error: ^.
jwasm(82) : Error A2209: Syntax error: �%
jwasm(83) : Error A2209: Syntax error:
jwasm(87) : Error A2209: Syntax error:
jwasm(197) : Error A2209: Syntax error: ��
jwasm(206) : Error A2209: Syntax error: JWASM
jwasm(208) : Error A2209: Syntax error: ��t
jwasm(209) : Error A2209: Syntax error: ��
jwasm(212) : Error A2209: Syntax error: ��v
jwasm(214) : Error A2209: Syntax error: �8
jwasm(216) : Error A2209: Syntax error: �
jwasm(219) : Error A2209: Syntax error: ��h
jwasm(220) : Error A2209: Syntax error: ��SQV����1��$1�1�����h
jwasm(221) : Error A2209: Syntax error: �…�u������
jwasm(224) : Error A2209: Syntax error: ��h
jwasm(225) : Error A2209: Syntax error: ���
jwasm(228) : Error A2209: Syntax error: ��h
jwasm(229) : Error A2209: Syntax error: �Y3
jwasm(230) : Error A2209: Syntax error: �����lf
jwasm(231) : Error A2209: Syntax error: ��tC4
jwasm(232) : Error A2209: Syntax error: �d�
jwasm(233) : Error A2209: Syntax error:
jwasm(235) : Error A2209: Syntax error: ������g
jwasm(236) : Error A2209: Syntax error: �<$
jwasm(236) : Error A2113: Too many errors
jwasm: 236 lines, 1 passes, 0 ms, 0 warnings, 51 errors
sha256sse.asm(48) : Error A2091: Language type must be specified
sha256sse.asm(314) : Error A2142: Unmatched block nesting: CalcSha256Sse
sha256sse.asm: 316 lines, 1 passes, 0 ms, 0 warnings, 2 errors
make: *** [sha256sse.o] Error 1 looks like a ton of misencoded unicode characters |
|
|
|
what's a name coin, I looked it up but I still don't get it.
I would also like an explanation or a link to one, I didn't understand the developer's words.
it's basically a DNS service based on bitcoin. you can use "coins" to register and renew domain names. |
|
|
|
Lie in wait - When miner finds a winning share, he doesn't submit it right away. Instead he pulls all his mining capacity (assuming he has extra capacity used elsewhere, perhaps specifically in preparation for this cheat) into this pool, using his "inside knowledge" that a winning share is imminent to increase his expected payout. what do you mean by that? here's my interpretation: 1. you find winning share, you don't report it 2. you take all of your miners off of the pool, and onto another pool am i getting this correctly? |
|
|
|
|
you can only use your IGP GPU (i believe) if it supports hybrid crossfireX. 3200 does not.
|
|
|
|
Lol at spending a billion dollars on a computer and "having energy efficiency in mind".
*energy efficiency "3GFLOPS/watt" |
|
|
|
lol, that guy can't spell (so much scribbles) |
|
|
|
|
well there's your problem:
http://"http//bitcoinbazaar.com/"
nice quotes :p
|
|
|
|
so you were the guy who was registering all the "short" domain names  |
|
|
|
|
kind of a noob question:
is there a way to see blocks that are maturing (less than 100 confirmations)? I've mined several blocks ("accepted" in poclm), but it's not showing up in my balance, nor is it showing up in my transactions list.
|
|
|
|
This system needs Faith
we can start with PGP signatures :p |
|
|
|
I posted before in a thread about "btc2" a similar idea.
The idea is that where bitcoin converts CPU/GPU power to coins, an alternative would be to convert network bandwidth to coins.
I'd prefer to implement this coining of bandwidth in Tor, so it could be called Torcoin. And because there would be consistent activity in an effort to mint torcoins, this might help protect against some of the correlational vulnerabilities which can defeat tor anonymity. But this is just a guess, I'm no tor expert.
I understand how to use a GPU to secure a blockchain... how do you do the same with bandwidth? Well that's the question now isn't it.. I'm just hypothesizing that its possible, not making a concrete proposal. So bitcoin mining expends CPU power with a probability of processing the correct block-chain hash for the next block in the chain. A vague and non-technical proposal for torcoin: Torcoin mining expends bandwidth with the probability of transferring/processing the correct (not CPU intensive hash of) the next packet-block in the packet-chain. So more bandwidth gives more probability of getting the key packet. Tor exit nodes would have an advantage over non-exit nodes in transferring these "solution" packets, since more packets travel through exit nodes (at least when accessing external/non-hidden services). This would give more incentive for the operation of exit nodes. Packets from tor users would be hashed by the proxying nodes attempting to mine the torcoins in the next packet-chain. The critical necessity for this system to function is that CPU power won't help find the next packet-block in the packet-chain, only bandwidth capacity. Additionally, torcoins could be spent by tor users for increased priority for their packets. So more torcoins spent by a user would enable greater tor network speed. And inversely, the operator of a tor hidden service would mine more torcoins, thus giving incentive to operate popular tor hidden services. Tor users without torcoins would get the default low speeds, but their packets would provide new torcoins for the network. So maybe the total amount of torcoins in circulation would increase proportionally to the bandwidth transferred within the Tor network, inflationary style. Or maybe the total torcoins in circulation could be limited absolutely, in the deflationary style of bitcoin. The main goal here would be to monetize anonymous bandwidth, the same way bitcoin monetizes CPU power. what's preventing me from setting up 10 computers, with 10 GB/s connections (to each other) to "simulate" traffic? |
|
|
|
I don't see how hashing data causes sentience. This thread reminds me of my previous computer, which was running Bitcoin 24/7.
One day I found that the computer had been siphoning off the transaction fees from the blocks that it was generating for me, and using the coins to buy upgrades for itself.
I discovered what was going on when I came home one day and found a technician installing an upgrade that had been ordered using my credit card number.
I decided to decommission the computer and replace it with a newer model. Unfortunately, the computer discovered my plans, and started behaving very erratically indeed. It modified my outgoing emails to cause the maximum amount of strife, so I backed up wallet.dat, unplugged the miscreant computer, and demolished it with a sledge-hammer.
On my new computer, I only run Bitcoin from a virtual machine image. It's totally not worth the risk to run Bitcoin on the raw hardware. But you can never trust these computers. Just the other day I noticed that it had signed up for a Blogger account and was making a lot of money from AdSense.
hahahhaa +1 |
|
|
|
|
the second one won't work, because shares expire every 10 minutes (approximately)
|
|
|
|
Let's make this system without extension. They have been an unnecessary overhead anyway.
So just 'google' instead of 'google.com'
Another incentive for people to adopt it.
+1 So Trends would be http://trends.google ? it will fail miserably when someone registers "com", "net", etc. |
|
|
|
|
Show Posts
