Show Posts
|
Pages: [1] 2 »
|
Still waiting 
|
|
|
True, but at least they are keeping the scammed ones updated: http://hashrack.com/Still no response from them...
|
|
|
No! " mi" Nakamoto! 
|
|
|
I joined the queue @ october, till then been trying to cancel my contract without any success, no replies from them... After all this 4 months, seems that we got scammed.
|
|
|
Greetings y'all, In September i've ordered an Hashpack of 5GH/s, paying the amount of 0.46 BTC. On the past 2 months i've been attempting to contact them in order to refund the spent value. There is no awnsers from them neither refund being made. 
|
|
|
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means. Gotta love freedom projects, going to hammer this toy and help you on github, Cheers. 
|
|
|
Western citizen of underprivileged countries
Love radicalism! I buy it all!
|
|
|
Sharky444 get the new GPU miner and mine, got it working!
|
|
|
Imagine a guy is mining a second blockchain since block 2 Now imagine he manages to make it longer (by mining or by finding a flaw in the mining process) that the one we currently see and he releases it Result: all transactions are reverted and the only one to have any bitcoins since block 2 is him
By adding a checkpoint at block n, you force your client to refuse chains if the hash for their block n is not the one of the checkpoint, so the guy can't revert the blocks older than n
Best imaginary explanation, then it would make sense to have a dynamic callback filling this checkpoints automatically by a consentual wallet analysis? There must be a way of having all the wallets posting/confirming same "N" from time to time, or block to block (every 1500 blocks for eg?) A second benefit is that you can skip signature verification. Checking that every transaction is signed properly is the major CPU load for downloading the blockchain.
The reference client still checks each block to make sure no double spends happened and that the minting rewards were valid, but it doesn't check that the transactions were properly signed.
Once it hits the last check-pointed block, then signature verification is switched on. This speeds up downloading the chain. It turned out that CPU load when checking the signatures was the bottleneck. Even though the chain is many GB long, network speeds were fast enough so that the CPU was the bottleneck.
The older your checkpoint is, the more signatures you have to check "manually".
It is possible to turn off checkpoints, if you want to fully verify the chain yourself. I don't know if they have a way to keep checkpoints but still check all signatures anyway.
Great, so this means we can setup new transaction fee's just by defining a checkpoint on the new TX block? Lovely, thank you both for the light...
|
|
|
Greetings, I've been messing around with "C" coding from different coin systems, trying to understand all the logic behind it. There is a subject that im not yet clear to understand, at checkpoints.cpp: ( 15000, uint256("0x00000082cab82d04354692fac3b83d19cbe3c3ab4b73610d0e73397545eb012e")) ( 30000, uint256("0x0000000af2f6e71951d6e8befbd43a3dac36681b5095cb822b5c9c8de626e371")) ( 45000, uint256("0x00000000591110a1411cf37739cde0c558c0c070aa38686d89b2e70fe39b654f")) ( 60000, uint256("0x000000000c067c5df98a8285ff045c3ffee46eb64b248bc6622f6bdceb8558be")) ( 75000, uint256("0x000000004ab2d277c8a056f55f32efa515a9931cb0404d60d0efc4f573412e66")) ( 90000, uint256("0x000000000cfe2ec9d27b784c2627c3864d26e5829cc5b18b4eff37d863ed0675")) ( 105000, uint256("0x00000000b0480b6a15fee32ee47d4b30dc82dc44ab680f1debb2ce2b13f73aab")) ( 120000, uint256("0x00000000d843c5c818620d00c9352e0cc3bbf7fdb9d69093795fbfffff13c92a")) ( 135000, uint256("0x0000000292cb16d5935e015a786d33f3228da23d92dfeb6ddff7249a3227f956")) ( 150000, uint256("0x000000035d01ee7f75032c0293a7e6b1217d447fe3e000ede7911cb0520c60c7")) ( 165000, uint256("0x00000001e790d65de9541af419465338220de69e3ffcbda427af2fc94741d321")) What is the point of adding checkpoints? can someone explain me the theory? Cheers
|
|
|
Im trying to get test done under a fresh Windows XP. It all runs fine until 4a(Building Daemon part), returning the following error: c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_system-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_filesystem-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_program_options-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_thread-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_chrono_options-mgw45-mt-s-1_50 collect2: ld returned 1 exit status mingw32-make: *** [litecoind.exe] Error 1 (I've also tried without enviromnent) It can not find the boost libraries... try the build boost batch (is there an error?) and then build daemon / build qt Giving you my feedback under this subject, i found out your batchs are not friendly with "spaces" on folder names, like "Program Files". Managed to workit out by moving my coin folder to c:\, yet some other stuff happened i will try to fix it and repost feedback.
|
|
|
Im trying to get test done under a fresh Windows XP. It all runs fine until 4a(Building Daemon part), returning the following error: c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_system-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_filesystem-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_program_options-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_thread-mgw45-mt-s-1_50 c:/ming/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lboost_chrono_options-mgw45-mt-s-1_50 collect2: ld returned 1 exit status mingw32-make: *** [litecoind.exe] Error 1 (I've also tried without enviromnent)
|
|
|
 I guess your intention is saving alot people right now and will in the future  Great Job!
|
|
|
2much love in this thread. Binary Coin ping-pong clean style, FTW! You are right about what they did to us, but there is always a cure within you 
|
|
|
Alot of Open-Knowledge in this thread!BTC)
|
|
|
The usage of peer-to-peer system is being explored mostly by those people in the dark, away from forums/coffe-time theorists... Has you said you also been in the dark, this gave you the opportunity to step back and have a widder vision about the whole concept of peer to peer hashing, there are still alot of projects to be done, but you gave a great example, congratz for that. Anything you need from Logics to Creativity make contact. 
|
|
|
I find your idea very Creative and Logic! Looking forward to hear about it. Congratz for creativity good luck for making it happen
|
|
|
Cryptsy is a coin-exchange market.
Good Job
|
|
|
Greetings, I am here to theorotise with you about the safest way to build a public crypto-currency credit project.  | On the past months, i've been providing credits to close people, meanwhile i needed to track all the clients, timelines, values and quantities, so i took some time to build this personal app, with notification system and some other useful functionalities. The people i've been crediting, seem to target ASIC investments, leaving me has a happy crediter for knowing their investing on something they could actually pay me after. |
Now im heading for a public project, Credit Requesters and Credit Providers would be the main role of the project, but the vulnerability of this system is centered on Requesters. This requesters would need some proof of future payback, since Identity isn't the goal of bitcoin i wouldn't like to implement the need of personal information. Credit Provider will be able to define credit plans with: - Amount of BTC - Payment Timings - Earning Percentage I would like to brainstorm about Credit Requesters, even with a reputation system alike, we need to ensure this anonymous credits are trusted. Would a Credit Requester system, based on reputation work if only approved by accepting 50% of the requested value @ 0 reputation? (new requesters) Would a Credit Requester system, work based on type of credits and proof of investments? (Order ID, Payments,etc..) During your reading got hitten by any storm lightning? (Idea) Please share... There is no release date for this project, since we have no vision of a stable system yet, but as soon as we got something, a timeline will be defined for development. Thank you, Open your mind. 
|
|
|
|