Bitcoin Forum
May 24, 2024, 11:16:16 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 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 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 »
1381  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 05:28:22 PM
So the solution is to continue to increase the block size as demand provokes this issue then?
I guess.. because what else? Are you going to appeal to people to do less transactions, hoping that it would solve the problem? Smiley
I don't believe you can i.e. convince satoshidice to drop down their lucrative business, just because other ppl's transactions are getting queued...
Why should they care anyway, if they pay the same fees as you do?
Since we don't have other solution at hand, scaling up the storage limits seems to be the only option ATM.
Unless we're OK with increasing the fees?
1382  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 05:20:49 PM
Not sure why everyone is so panicked.  We only orphaned 25 blocks and the only danger was that you would accept the coins minted in those blocks (all transactions using other coins would eventually end up in the other chain as well).  If we just followed the network rules and waited 100 blocks to accept minted coins then there was actually no danger at all.  What am I missing? 
You are missing the fact that it was a great opportunity to double spend any coins.
Once: you send 1000 BTC paying to merchant that uses bitcoin 0.8
Second: you pay the same 1000 BTC to another merchant who has an older client and thus is "looking" at the alternate branch, where the 1000 BTC has not been spent yet.
1383  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 05:09:54 PM
...

Also, I'm afraid it's very easy to say "just test for longer" but the reason we started generating larger blocks is that we ran out of time. We ran out of block space and transactions started stacking up and not confirming (ie, Bitcoin broke for a lot of its users). Rolling back to the smaller blocks simply puts us out of the frying pan and back into the fire.

We will have to roll forward to 0.8 ASAP. There isn't any choice.

I would like to understand with better precision what you mean by this.  Can you point to a particularly enlightening bit of documentation or discussion about this issue?
I believe he means that if you have a constant rate of 6 blocks/hour and a fixed number of max-transaction-per-block, when the number of transactions is going up, they eventually go above the "bandwidth" limit (which is: 6 * max-tx-in-block / hour) and instead of being mined at the time when they are announced, they are getting queued, to be mined later...
Which is exactly what I have been observing for the last few weeks - even transaction with a proper fee needed like hours to be mined.
And this is very bad.
Bitcoin really needs to start handling bigger blocks - otherwise soon our transactions will need ages to get confirmed.
The network will just jam, if we stay at the old limit.
1384  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 03:43:33 PM
How do i do a -rescan?
when you start bitcoin-qt (or bitcoin-qt.exe) add -rescan to the command line.
it will take much longer to start, but all the transactions inside your wallet should eventually appear confirmed, assuming that you see them confirmed at i.e. http://blockchain.info/


that fixed it, thanks for the tip... though do i need blk0001-3.dat? theres 3 files each being 2gb.
if you are talking about the files from the main data dir (not in the "blocks/" subfolder) - you don't need these for 0.8
they were only used up to 0.7.x and while using 0.8 you can just remove them.

but to be sure, better close your bitcoin client, move the files to some temp folder, start the client and see if it still works fine - if it does, delete the files, otherwise restore them.
1385  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 12:51:46 PM
How do i do a -rescan?
when you start bitcoin-qt (or bitcoin-qt.exe) add -rescan to the command line.
it will take much longer to start, but all the transactions inside your wallet should eventually appear confirmed, assuming that you see them confirmed at i.e. http://blockchain.info/
1386  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 12:39:32 PM
i have a bunch of unconfirmed bitcoins when i reverted back to 0.8
did you try to start it with "-rescan"?
1387  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 12:35:42 PM
A hard fork like this would require the intentional support of a majority of merchants.
Sure. But how is it unintentional to accept blocks longer than 250KB, after the "majority" (expressed in the hashing power) upgraded their clients to a version that accepts blocks larger than 250KB? Wink
And they upgraded it not because they had no reason - they actually had a very good reason.
1388  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 12, 2013, 12:18:07 PM
The only question is when does it happen and who will lose out because of it.
The really important question is what would have happened if there wasn't a coordinated effort to help the "correct" fork?
The longer one would have won.
Depending on how much power is already at the new clients, this could have disabled the old clients from the network - made them obsolete.
Which maybe would have been a good thing, considering that this needs to happen anyway, if we don't want to wait weeks for our transactions to get mined, in a month time or so.
1389  Economy / Securities / Re: ASICMINER: Entering the Future of ASIC Mining by Inventing It on: February 28, 2013, 05:02:48 PM
awesome!
good night, friedcat Smiley
1390  Economy / Securities / Re: ASICMINER: Entering the Future of ASIC Mining by Inventing It on: February 15, 2013, 12:00:53 PM
Thanks. I dont like the thought that the money isnt paid back and friedcat, who isnt guilty for this has to pay. Its a big amount of real money.
Yea, I agree with you, but it was friedcat's decision (nobody has pushed him into it), so we can only thank him for being so generous Smiley
1391  Economy / Securities / Re: ASICMINER: Entering the Future of ASIC Mining by Inventing It on: February 15, 2013, 11:42:43 AM
Maybe i missed it but i wonder if nefario paid the btc from glbse back already. Is that done or will asicminer have to compensate a loss there?
It was already said. Nefario is still holding 1688.188 BTC that used to belong to ASICMINER, but friedcat has put his own money to cover this missing amount.
When nefario pays back, this will go to reimburse friedcat.

In other words: nefario did not pay back, but ASICMINER's funds are all there, after friedcat covered the frozen funds from his own pocket.
1392  Bitcoin / Bitcoin Technical Support / Re: [PHP] Generate a sendmany with multiple outputs to the same address on: December 31, 2012, 06:18:58 PM
What was the workaround?
Well, it's a workaround only if you're fine with single transaction per a recipient address (I was).
In such case, just sum up the amounts using a map with the destination address as the key.
Something like:
Code:
$addrs = array();
for(...) {
    $destaddr = ...
    $amount = ...
    if (array_key_exists($destaddr, $addrs)) {
        $addrs[$destaddr] += $amount;
    } else {
        $addrs[$destaddr] = $amount;
    }
}
After this you have only single addresses in $addrs (with the amounts summed up), so just:
Code:
$rpc = 'sendmany "'.ACCOUNT.'" \'{';
$com = false;
foreach(array_keys($addrs) as $da) {
$am = round($addrs[$da], 8);
if ($am>0) {
if ($com)  $rpc .= ', ';
$rpc .= '"'.$da.'":'.sprintf('%.8f',$am);
$com = true;
}
}
$rpc .= '}\'';
1393  Bitcoin / Bitcoin Technical Support / Re: [PHP] Generate a sendmany with multiple outputs to the same address on: December 30, 2012, 05:20:43 PM
Yeah, it's a bummer that you cannot specify the same address twice - I once suffered from this as well, but a workaround was fairly simple, especially in PHP.

A bigger issue I've had with sendmany is that the command requires the "<fromaccount>" parameter and you cannot just say to it like "whatever account"...
So the way I use my client, having coins spread across several "accounts" (which I personally only use to label addresses), then it seems like someone had made this parameter mandatory just to piss me off... Wink
1394  Economy / Securities / Re: Starting a new FPGA mining farm/contract! Cognitive Resurrected on [BTC-TC] on: December 24, 2012, 07:40:12 AM
Since this is a thread about Cognitive, I will refrain from pointing out your admittance of being unprofessional.
Well... but since, despite of refraining, you have pointed out me being unprofessional, let me tell you that your friend Nefario had been all about being professional, and look what has happened now. Smiley

Besides I assure you that I am very professional - I just don't work in sales, nor in marketing, neither in any other useless profession that would require me to sell bullshit.
I have a good product and so I don't even need to advertise it.
For this product, it is enough to just wait for people to learn. Because similar problems with other asset exchanges seem inevitable to me, and it is just a matter of time before another gets hacked or something, and again nobody will be able to prove anything.

How many exchanges need to blow up before people finally learn how to protect their assets?
Hard to say, but from what I see I should probably say: too many... Smiley

Anyway, you already said several times that you're not going to use my idea, because you find its inventor and developer unprofessional.
Fine, then don't use it - who asks you to?
I'm not even sure why you are repeating yourself again, but you called it - so here I came.

Therefore answering your insinuations, I would like to make it straight for other people, such who would actually be interested in parking their bitcoin-based assets outside traditional exchanges, that Cognitive is welcome at assets-otc. And I don't expect delisting it ever, because doing business with Garrett has always been my pleasure and I believe it was also the other way around. So I cannot imagine any reason for it to change.

And you stochastic - you are just talking bullshit, as you usually have.
1395  Economy / Securities / Re: Starting a new FPGA mining farm/contract! Cognitive Resurrected on [BTC-TC] on: December 23, 2012, 08:26:45 PM
As you can see Garr, poitr_n is pretty unstable.  As you would know, I was asking what a plan B would be for Cognitive before Nefario even went berserk.  poitr_n is the type of person that will attack anyone that questions his decision making, much like Nefario.  It is unfortunate because I am only interested in improving and advocating for the exchange markets of stocks and bonds trading for cryptocurrencies.  I even linked to poitr_n's post about #assets-otc from my market indicator site (stochastically.com) after GLBSE was shut down because I thought it would be a great alternative, until the craziness that occurred.  Maybe that person's asset was delisted due to some claimed scamming, but to me it happened because he posted about Open Transactions on in the forum post about #assets-otc.  If we had sane and profession people running these exchanges (take burnside as an example) I think these exchanges could do a lot of good.  I think competition is a good thing and I wish exchange operators would work together or at least be humble and respectful.

But I am glad you only list it as an option and not recommending the place.  As you can see it is a warning to anyone that might want to use #assets-otc.
I think you are talking to me, though addressing your speech to someone else. In which case, I am going to do exactly the same Smiley

Why am I unstable?
The only reason you have to support the theory that I am unstable is that I delisted your friend's asset from my generously free contract management service, after he had offended me.
So what is so unstable about it?
If Garrett had ever offended me, I would have delisted his asset as well - surprise? I don't think so.
And moreover, I don't think he will ever offend me because he is a normal honest guy who can listen to reason and never talks bullshit. So I believe he will listen to my reason, publically if needs so. And you - you keep selling bullshit to him, but don't dare to use my name with it, hoping for no reaction. There will always be a reaction - you can bet on it.

And, by the way, let me tell you once again that assets-otc is nowhere about anyone's trust to me.
I'm not holding anyone's balls for any moment - I'm only storing contracts.
Being delisted at my page does not mean anything.
In fact soon I'm going to publish the source code so anyone can get his shit and just start it at his own server, if he knows what php and mysql is.
1396  Economy / Securities / Re: Starting a new FPGA mining farm/contract! Cognitive Resurrected on [BTC-TC] on: December 23, 2012, 11:19:31 AM
Be careful
https://bitcointalk.org/index.php?topic=105437.msg1287486#msg1287486
To see why it was delisted, read the post above the one linked.
Smiley
Said a guy who used to be Nefario's big advocate - at the same time when I was already calling him a crook who was backing Goat to cheat his customers, stole 3000 ASICMINER shares, and god knows what else he did to screw over GLBSE users...

There are obviously people who will never learn, like you stochastic, but trust me, dear: I am the last person who would be trying to educate you.

So despite of your confidence in Nefario's honesty, I did not listen to you but chose listening to my reason and thus already in August I preemptively parked my modest share in Garrett's business.
Such a crazy move allowed me to keep receiving the divs while everyone else was shaking their pants  worrying whether Nefario would give the shareholders list or not. The list which BTW nobody can still be sure to be correct. In fact it does not look correct at all if you know that 3 days before GLBSE went muted there were only 7870 COGNITIVE shares, Garrett told you that he did not sell anything outside the market, and if you see at the twitter feed that the total trading volume for that last 3 days was.... below 200 shares!
So how the hell did it end up with 8616 shares?  I guess there must be a perfectly reasonable answer for that, but unfortunately no way to verify if such an answer would be true.
My blind shot is that the extra new shares just ended up as Nefario's "claim", but since we cannot prove that, all we can do is asking Garrett "how has he invested the money acquired by selling the 746 new shares?" - and then, he will most likely answer with "what money?" Smiley And not because he is the one who screwed us here - he just cannot do anything else in this circumstances, having no proofs for anything that happen on the exchange, because no single transaction can be proven.

So yeah: be very careful with having PGP signed contracts for what you own!!!
Just listen to stochastic - the guy knows what he is talking about and he will give you the best advise, as he always had yet back in the GLBSE times. Smiley


I like the colored-coins idea.  I think that has a lot of potential.
Yeah.
And I like the idea of spending Christmas on a white sanded sunny beach, sleeping under a palm, smoking joints, soaking cold bier, watching crabs and snorkeling with fishes...
But the reality is cruel and so you can't always get what you want.
Or skipping the metaphors: colored-coins is just a theoretical idea, while assets-otc is already a practical reality.

So if you prefer colored-coins then be my guest: keep waiting for your dreams to come true, hoping that the bitcoin enterprise that you are currently in, based on exactly the same security concept as the one that screwed you before, won't just blow up one day, right into your face.
And stay away from simple PGP-signed contracts, because they are so inconvenient that only crazy people use them Smiley
1397  Bitcoin / Project Development / Re: #assets-otc - Contract Management System on: November 25, 2012, 08:20:38 AM
I wish it was possible to provide a web browser with PGP functionality without the binary plugins, but unfortunately our modern and super advanced HTML 5 compatible browsers support basically everything I man could imagine; drawing canvas, vector graphics, A/V streaming with advanced codecs, OpenGL acceleration, and all the other fancy shit... but not a good old fashion RSA cryptography, neither a big numbers math.

You might want to have a look at this:

http://developers.slashdot.org/story/11/11/22/0422223/openpgp-implemented-in-javascript

The project referenced within has moved:

http://www.openpgpjs.org/
Thanks.
This projects looks quite promising and it performs not too bad... at least in Chrome, with 2048b key, on my i5 CPU Tongue

Unfortunately it does not work yet, because whenever I clear-sign a message that contains more than one end-of-line character, it does not verify later on.
See an example, if you wish: http://www.speedyshare.com/Gm2gU/openpgpjs-test.zip

Moreover, keeping the private keys in the browser's local storage and entering the password to unlock it via a browser's form, is not a kind of security that I would like to encourage.
So for now I will rather stick to the NAPI plugins - faster, safer and just works.
1398  Bitcoin / Project Development / Re: #assets-otc - Contract Management System on: October 27, 2012, 06:05:19 PM
Today I released an extension for Chrome browser which automates all the gpg related stuff.

Having the extension installed in your browser + GnuPG in your OS (armed with your private key), you basically don't need to use command line anymore with assets-otc.com - just enter the password for your key when asked. It's pretty convenient.

You can read more about the extension and download it from its GitHub repo: https://github.com/piotrnar/aotc4chrome

Unfortunately some binary files are involved - it was the only way to go.
I wish it was possible to provide a web browser with PGP functionality without the binary plugins, but unfortunately our modern and super advanced HTML 5 compatible browsers support basically everything I man could imagine; drawing canvas, vector graphics, A/V streaming with advanced codecs, OpenGL acceleration, and all the other fancy shit... but not a good old fashion RSA cryptography, neither a big numbers math.
So as much as I could research it, there is no way to write an RSA library in JavaScript.
Well... technically it is possible to write such library, but it would be so slow that signing a message with a regular 2048 bits key would be taking like days or weeks to complete.
1399  Bitcoin / Project Development / Re: #assets-otc - Contract Management System on: October 22, 2012, 04:34:17 AM
@EskimoBob you asset has just been desisted from #assets-otc and you will never be allowed to list any assets at this service.

I sent you the history of your asset by email - all 3 transactions and both the pgp keys.

Now go licking some more goats' balls.

Thanks for the information, I will stay away from your services for now on.
You're welcome.
Thanks for staying away from my services.

I'm really trying hard to make this project completely different from all the other shit holes, like i.e. GLBSE used to be.
And I remember very well that all of you guys used to be a huge fans of Nefario, back in the old times when I was saying that he was a thief and a liar - and in the response you were calling me a troll who did not know what he was talking about... And then I told you that the time would show... and then the time did.

So you either have not learned the lesson (meaning: extreme stupidity), or you have other reasons (most likely: dishonesty) - either way you are not welcome at assets-otc, since stupidity neither dishonesty of asset issuers is not going to be tolerated there.

Hope that's finally clear now, whose assets are welcome and whose are not, so there will be no more disappointments.
1400  Bitcoin / Project Development / Re: #assets-otc - Contract Management System on: October 21, 2012, 11:01:35 AM
So people like Eskimobob, Me, Nefario, Theymos, and who else?
Anyone who either has been dishonest or endorses people who have been dishonest.


Would it not just be faster for you to list people you are okay with?
My mother used to say that people perceive others by who they are themselves.
So I understand your rationalization of why you think that all the people except few would be dishonest, but I don't share your opinion about this and I believe that there are more honest and smart, rather than dishonest and stupid, people living on Earth...
So no, it wouldn't be faster to list few billions of people.


Also can I read your TOS?
I don't have TOS and I don't plan to have any.
Do you have a problem with that? Smiley
Pages: « 1 ... 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 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 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!