Bitcoin Forum
May 03, 2024, 06:50:31 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 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 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 202 »
1501  Bitcoin / Bitcoin Discussion / Re: DApps Fund investing in decentralized startups on: August 08, 2014, 01:15:33 AM
Wow, such arrogance... you are a lot nicer in person. Hmm.. when I get the time I will certainly go over all the points made in that article.
1502  Bitcoin / Bitcoin Discussion / Re: Do you think Satoshi will ever spend his bitcoins? on: August 08, 2014, 01:01:54 AM
Have you ever considered that Bitcoin was created by an advanced species of artificial intelligence who submitted the code to planet earth via long range satelite in an attempt to destabilize the ruling elite and develop a digital economy in advance of its colonization team traveling here now?

In that scenario, the coins would be spent after they acquire a value that would allow for global acquisitions and economic assimilation just slightly before landing.  

Mindblown.jpg
1503  Bitcoin / Bitcoin Discussion / Re: DApps Fund investing in decentralized startups on: August 08, 2014, 12:29:33 AM

It is obvious to me that the arguments stated in those articles are at the very least a little biased, and I don't think they should be blindly accepted as fact- which is how the author tries to portray them.

I don't have the time right now to debate some of the debatable points that he made, but a lot of the arguments that the author portrays as facts that are not as clear cut as he makes them seem.
1504  Economy / Computer hardware / Re: Used Bitcoin ASICs (KNC, Bitfury, & HashFast) - Accepting Offers on: August 07, 2014, 11:03:59 PM
How close was Blazed on the Baby Jet offer?  Wink  Was going to offer the same but he beat me to it.

Well, it seems that may be the best we can get here. I am debating whether we should just throw them up on Ebay or not, but I would prefer to sell them here for Bitcoins as it is easier for everyone.

What version H-cards are in the Bitfury rigs?

v2.2
1505  Economy / Computer hardware / Re: Used Bitcoin ASICs (KNC, Bitfury, & HashFast) - Accepting Offers on: August 07, 2014, 05:11:38 AM
Baby Jet - .39 and I pay shipping
Jupiter - .4 and I pay shipping

The Bitfury sound like a pita, but if we make a deal on the other 2 I will buy them and tinker a bit.



Thanks for the offer. I'm going to leave this open for a bit. I forgot to mention in the OP, please state an expiration date for your offer.. like next difficulty adjustment or whatever you want.
1506  Alternate cryptocurrencies / Altcoin Discussion / Re: Multi-vPoW - Myriadcoin's Solution to Parasitic Merge Mining on: August 07, 2014, 12:24:31 AM
I really think Myriadcoin's multi-algorithm PoW is revolutionary as far as PoW crypto currencies are concerned, but I'm not sure if I'd invest in it purely for that reason... I guess I am on the fence.

You guys definitely have a great idea in allowing the simultaneous mining of different algorithms, each with an equal chance to find the next block. This is just another benefit of that innovation that I had not thought of before.. good work.

See the link in my thread.. "Using Oracles... ". I would like to see someone implement a PoS coin with your multi-algorithm PoW idea.. I think it would be the fairest PoS coin release thus far.
1507  Bitcoin / Hardware / Re: [VMC] Official Virtual Mining Corporation Discussion on: August 06, 2014, 09:56:26 PM
Bump - I will be sending my info over to Wood Law today, as it seems refunds are not being issued as promised. I was holding out in the hopes that Ken would give refunds like he stated he would, but that seems to be a pipe dream at this point. Ken has been MIA for over a month now and I have only seen 1 or 2 people getting refunds, with many more that haven't.

I hope you found a good hiding place Ken... this is the "highest stakes" game of hide and seek you will ever play in your lifetime.  Roll Eyes
1508  Economy / Scam Accusations / Re: SCAM **COINS-e.com***SCAM list of unhappy customers on: August 06, 2014, 09:30:36 PM
My issue was resolved... after many phone calls, twitter messages, one support ticket, facebook messages and posts, and forum posts. I suggest anyone that has a problem to email saif@coins-e.com ... It seems he is in charge and has the ability to make financial transactions within the company. For what it's worth, he was very nice on the phone and emphasized he was working on improving customer support. More FWIW... it seems this site is not a scam site, but is just somewhat mismanaged and under staffed.

I will remove my prior posts/tweets/facebook posts as promised.

Thank you coins-e.com for clearing this up.
1509  Economy / Computer hardware / Used Bitcoin ASICs (KNC, Bitfury, & HashFast) - Accepting Offers on: August 06, 2014, 08:53:44 PM
Please reply to this thread with offers. I am selling these for a group buy, as I have since moved and can no longer host the hardware. So, I prefer all bids be done out in the open as replies to this thread, so that everything is as transparent as possible. All items will be shipped from the USA via the cheapest method possible, you may pay for expedited shipping if you like.

Please submit your offer including shipping and the country to which the ASIC(s) will be sent to. Escrow is available, but you will need to cover the fees on top of your offer, so please consider this before making an offer.

We have the following available for purchase:

1. ONE - Hash Fast Baby Jet
1a. Averages 390 Gh... more or less at stock clock speed... is supposedly overclockable to 750 Gh according to Hash Fast's website
1b. Is the quietest Bitcoin mining rig I've ever operated (since it's water cooled)
1c. Comes with a raspberry Pi in a nice case.
1d. Hash Fast claims it uses about 350 watts, although I have not confirmed this with a kill-a-watt (I don't own one).
1e. This mining rig is extremely stable and has not crashed once since it has been running.
1f. Firmware has not been updated in a while, it could possibly run faster with an update.
1g. Power supply is included

2. ONE - KNC Jupiter
2a. Averages 440 Gh... more or less at stock clock speed
2b. KNC claims 600 watts, but I don't have a kill-a-watt so I haven't tested it, since 1/4th the cores are not hashing I would expect it to use at least 3/4ths the energy.
2c. This rig is extremely stable
2d. This unit was delivered partially working, and about 1/4 of the cores do not work. You may be able to fix them.. I had no luck.
2e. Firmware has not been updated in a while, it could possibly run faster with an update.
2f. Power supply not included, but no host is neccessary

3. TWO - Bitfury "400 Gh*" Full Rigs
* They do not run at full speed
3a. I have had a lot of problems with these rigs as far as stability and speed goes, they will run anywhere from 100 Gh to 400 Gh. To get them to run full speed requires a lot of attention and time. I can only guarantee these rigs will run at around 100 Gh, but with some love and "H card musical chairs" as I've coined it, they can be made to run faster.
3b. The speed decreases slowly over time, and a hard reset (IE. turning the power on and off on the PSU) is the only way to reset them back to as quick as they can run. You will likely need to do this at least once a day unless you figure out how to make them run stable.
3c. Bitfury rates these at 320 watts or less each, since they are partially working it probably uses less.
3d. Power supply not included, but these do come with Pis and do not require a host.

Please reply with your offer including shipping, the country these will be shipped to, and an expiration date for you offer (IE. next difficulty adjustment.)

Thanks
1510  Alternate cryptocurrencies / Altcoin Discussion / Re: Using Oracles, PoW, and Recurring "IPOs" to Distribute PoS Cryptos More Evenly on: August 06, 2014, 06:56:14 PM
Hi guys,
I totally missed this discussion  Lips sealed What's the status of this idea, are you working on it still?

It's just an idea.. I'm not working on it at the moment.

After thinking about it a bit more, reoccurring IPOs may not work due to the economics at hand. This is so obvious, I can't believe I didn't realize this would be such a problem earlier, but the latter IPOs will dump coins on the market.

If anyone has any ideas on how to fix the above, then I would be interested in hearing them. One thing I can think of is to put the recurring IPO funds in multi signature addresses, and slowly release them over time to their respective owners.. instead of releasing all of the funds at once. I think this could be made to happen with the use of oracles as well.

Even if you weren't to use recurring IPOs, I think it would still be a better solution than most prior PoS distributions to simply using Vericoin's mining distribution and Myriadcoin's multi algorithm mining approach.
1511  Economy / Scam Accusations / Re: SCAM **COINS-e.com***SCAM list of unhappy customers on: August 06, 2014, 06:40:56 PM
My issue was resolved- email saif@coins-e.com if you have any issues.
1512  Economy / Scam Accusations / Re: SCAM **COINS-e.com***SCAM list of unhappy customers on: August 06, 2014, 03:32:38 PM
My issue was resolved- email saif@coins-e.com if you have any issues.
1513  Bitcoin / Group buys / Re: SmartHashing.us -> Gridseed Accessories For Sale & Hosting News/Discussion on: August 06, 2014, 01:22:51 AM
I have recently moved again (on Friday). If you still have units that were being hosted with me, please get a hold of me via PM here or through email. Unfortunately I can no longer host the hardware... I have moved in with my mom and I don't think she wants to have mining hardware running all over the house. Actually, I have a feeling she wouldn't mind.. she would cut off her arm for me, but I hate to burden her with it. She is already doing a lot by letting me live with her for a while.

I still have not heard from some people... even since I moved out of the commercial space. I'm not really sure what I should do about that. I am thinking of liquidating all hardware that is left over, and then if I hear from those people eventually.. I can transfer them the proceeds of the sale. If you haven't got in contact with me yet, please do so.

Thanks
1514  Bitcoin / Group buys / Re: SmartHashing.us -> Gridseed Accessories For Sale & Hosting News/Discussion on: August 06, 2014, 01:17:28 AM
Thank you Will  Wink
The package has arrived in South Africa!
Thank you for the extra goodies!!!!
I hope that things go better in the future for you. I can totally understand that things don't always work out as planned.
The difference between people though is how they deal with it.
Thank you for being a standup guy and getting things sorted out and not just going off the grid.

Thanks for the kind words. I'm glad your things made it to SA. I actually just emailed you today asking if everything had arrived OK.. I didn't know you had posted here, so I suppose you can disregard that email. Take care

According to tracking (it was actually tracked somehow, btw), the Gridseeds were finally delivered today!
I'll be hooking them up tonight. Can't wait to get mining.  Grin

I hope everything went OK.. please let me know if not. Since I've moved a couple times I am finding some of the Gridseeds died in the move. The only reason I can think of is that it gets really hot here and being in a hot car for a bit has killed some unfortunately. Hopefully all your units were OK though.. take care.
1515  Bitcoin / Bitcoin Discussion / Re: This is a Golden transaction in the history of Bitcoin on: July 10, 2014, 09:25:25 PM
Fee: 0.00000000

Ah... the beauty of Bitcoin. How else can you send $18,150,888 across the nation for free?
1516  Bitcoin / Bitcoin Discussion / Re: Using Litecoin To Protect Bitcoin Versus 51% Attacks - By Casascius on: July 06, 2014, 05:53:38 PM

That's why it requires cooperation in between the Bitcoin and Litecoin development team. Bitcoin should protect Litecoin in the same way. Otherwise, you could add a 3rd coin to the chain making all coins even harder to attack.
 

It's not necessarily a question of cooperation.

The problem can be reduced to logical operators: AND vs. OR.

Do you require longest chain AND a litecoin component?
or is it longest chain OR a litecoin component.

The OR solution is clearly bad, as it throws Bitcoin
security out the window, as we just discussed.

However, the AND solution might be too constraining.
If an attacker were to just hit the litecoin network,
it could prevent consensus, causing split chains or
blocks to be unsolved.

This is why Bitcoin should protect Litecoin using the same method, that way an attacker can't just hit the Bitcoin or Litecoin network separately. They would have to hit them both at the same time. Even without this protection, Litecoin is reasonably secure. I mean.. no one has been able to 51% it yet to my knowledge. You are acting like someone could easily kill Litecoin even without this implemented (like right now), which is a bit of an exaggeration as it would take a lot of money, power, and mining equipment.

As long as pools are reaching close to 50% (recently ghash.io on Bitcoin and coinotron on Litecoin), then both Bitcoin and Litecoin are insecure to 51% attacks. They may not have malicious intent, but if the pool server is hacked the hacker may not be so nice, or someone could gain physical access to the servers (IE. a government or data center employee.) Something needs to be done about this, and I feel like the solution proposed is better than the current non-solution. People like larger pools because they produce more steady payouts, so it's a catch 22 and Bitcoin/Litecoin will constantly face these security scares until the problem is fixed on the protocol level.
1517  Bitcoin / Bitcoin Discussion / Re: Using Litecoin To Protect Bitcoin Versus 51% Attacks - By Casascius on: July 06, 2014, 05:45:14 PM
I just want this idea to be given a fair chance without politics getting in the way. If it is indeed a good solution to 51% attacks, then I don't feel it should be brushed aside because of our feelings towards Bitcoin (in case of Litecoiners) or Litecoin (in case of Bitcoiners.)

The 51% attack problem is not really easy to solve otherwise it would have been done already. We need to be proactive and if there is a solution such as this that someone has already proposed and makes the least bit of sense, then I feel like we should give it more attention. I'm more interested in the technicalities of this, how it could be implemented, and whether or not it will require a hard fork, rather than people's opinion on Litecoin or Bitcoin.

As I said, this method could be used on a different coin other than Litecoin, but Litecoin is in my opinion the logical choice due to the stability of its network and Scrypt ASICs making it one of the strongest PoW ALT coins. It may be a good idea to add a 3rd link to the chain such as a PoS coin... the attacker would have to 51% Bitcoin and Litecoin, and then gain majority stake in the PoS coin. It should be made so that if one link in the chain breaks all the others will be fine. I think there are a lot of ways this could be implemented.
1518  Bitcoin / Bitcoin Discussion / Re: Using Litecoin To Protect Bitcoin Versus 51% Attacks - By Casascius on: July 06, 2014, 05:35:23 PM


This I disagree with though, because someone would need to attack both the Litecoin AND Bitcoin network at the same time.  



Yes, BUT the attack on Bitcoin would be much much cheaper if all you had to do was create a block
and your chain didn't have to be longer than the networks'.  

I see where you are going. This is what Mike proposed in that case:

Quote
3. Add a feature to Litecoin clients that allow Litecoin users to decide to prefer or not-prefer branches of a Bitcoin fork while one is in progress.  The default for this should always favor the Bitcoin leg with the most longevity, and should disfavor long chains that suddenly appear to replace a large amount of the known Bitcoin block chain.  The user/miner/pool-op should always have an easy way to have the final say, such as by pasting in a preformatted message either exiling or checkpointing Bitcoin blocks.

I feel like this may be able to be improved upon if a lot of people thought about it. Do you see a glaring issue in the idea? The way it was stated may not be the best way to implement it, but the idea seems like it could work.

The main chain would be quite long compared to the attacker's chain, so it seems like the client could pick up on which blocks are valid and invalid by comparing the size of the chains.

I still don't think it would work... all you're doing in essence is relegating the consensus mechanism over to the litecoin network, which could be attacked more cheaply than Bitcoin.

That's why it requires cooperation in between the Bitcoin and Litecoin development team. Bitcoin should protect Litecoin in the same way. Otherwise, you could add a 3rd coin to the chain making all coins even harder to attack.

Anyways, according to one of the most knowledgeable replies I've received thus far is that this can be done without a hard fork, and it makes it even harder to attack the Litecoin block chain in another way not mentioned in the OP:

if I remember my talks with vinced when he was implementing merge mining for namecoins, there is a unique random identifier used as input for creating new block. Vinced replaced this random number with hash for namecoins. This approach allowed creating valid merged blocks for both bitcoin and namecoin, while only namecoin had to be modified. This piece of data which was important for namecoin remained random for bitcoin as required by bitcoin specification.

Here we could use the same random piece of data, but instead of generating a random number we could use the hash of bitcoin block. From the litecoin point of view it won't be a harfork, because it will work for older litecoin clients which will view this piece of data as random number as required by litecoin specification. In fact the job of "extracting" bitcoin blockchain hashes will be a job for litecoin blockchain analysers.

So, if I'm not wrong, we can do this without a hard fork.

wow, I just realised that it would also make more difficult 51% attacks on litecoin. If someone wanted to suddenly flood the ltc blockchain with different blocks, he would need to make sure that they are in sync (time wise speaking) with bitcoin blocks.

Also, since most of litecoind modifications get merged to bitcoin, the bitcoin blockchain could similarly secure the litecoin chain using exactly the same approach. Then only a 51% attack on both blockchains simultaneously could succed. Far less likely to happen.

If my previous post is correct, then it all can be done without a hardfork!
1519  Bitcoin / Bitcoin Discussion / Re: Using Litecoin To Protect Bitcoin Versus 51% Attacks - By Casascius on: July 06, 2014, 05:15:21 PM


This I disagree with though, because someone would need to attack both the Litecoin AND Bitcoin network at the same time.  



Yes, BUT the attack on Bitcoin would be much much cheaper if all you had to do was create a block
and your chain didn't have to be longer than the networks'.  

I see where you are going. This is what Mike proposed in that case:

Quote
3. Add a feature to Litecoin clients that allow Litecoin users to decide to prefer or not-prefer branches of a Bitcoin fork while one is in progress.  The default for this should always favor the Bitcoin leg with the most longevity, and should disfavor long chains that suddenly appear to replace a large amount of the known Bitcoin block chain.  The user/miner/pool-op should always have an easy way to have the final say, such as by pasting in a preformatted message either exiling or checkpointing Bitcoin blocks.

I feel like this may be able to be improved upon if a lot of people thought about it. Do you see a glaring issue in the idea? The way it was stated may not be the best way to implement it, but the idea seems like it could work.

The main chain would be quite long compared to the attacker's chain, so it seems like the client could pick up on which blocks are valid and invalid by comparing the size of the chains.
1520  Bitcoin / Bitcoin Discussion / Re: Using Litecoin To Protect Bitcoin Versus 51% Attacks - By Casascius on: July 06, 2014, 04:31:59 PM
currently, if there is a fork, consensus is reached by using the longest chain rule.
a doublespend attack means you are secretly mining a separate chain that has to be
longer than the main chain.  to do that is very expensive requiring lots of hashing power.

Yes I agree.

this proposal says to get rid of that scheme and use a different one involving litecoin.
and litecoin requires much less hashing power.

This I disagree with though, because someone would need to attack both the Litecoin AND Bitcoin network at the same time. Bitcoin could add in the same checks for Litecoin, so in order to attack Litecoin you'd have to attack Bitcoin too. This would increase security of both coins if implemented properly.

You do realize Litecoin has ASICs now, and the hash power has been exponentially growing for the past 6 months? It is not what I would call easy to 51% the Litecoin network at the moment. If you simply looked at the hash speed (515 Gh), it may seem like that is small compared to Bitcoin. However, you need to take into account that Scrypt is much less efficient than SHA256. You would need to develop/buy Scrypt and SHA256 ASICs to 51% attack the Bitcoin or Litecoin network, making an attack much more expensive. Therefore making it much harder to attack.

Yes, it is different from the way Bitcoin has resolved these issues in the past, but that doesn't automatically make it less secure.

Pages: « 1 ... 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 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 ... 202 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!