Bitcoin Forum
September 25, 2020, 11:25:36 AM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 [632] 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 ... 2083 »
  Print  
Author Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency  (Read 4628805 times)
Kuriso
Hero Member
*****
Offline Offline

Activity: 533
Merit: 500


View Profile
September 04, 2014, 09:31:29 AM
 #12621

why the fuck does mintpal not stop trading?

no admins active in the IRC...
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1601033136
Hero Member
*
Offline Offline

Posts: 1601033136

View Profile Personal Message (Offline)

Ignore
1601033136
Reply with quote  #2

1601033136
Report to moderator
1601033136
Hero Member
*
Offline Offline

Posts: 1601033136

View Profile Personal Message (Offline)

Ignore
1601033136
Reply with quote  #2

1601033136
Report to moderator
1601033136
Hero Member
*
Offline Offline

Posts: 1601033136

View Profile Personal Message (Offline)

Ignore
1601033136
Reply with quote  #2

1601033136
Report to moderator
xulescu
Sr. Member
****
Offline Offline

Activity: 263
Merit: 250


View Profile
September 04, 2014, 09:33:39 AM
 #12622

please help me out guys

its been more than 2 weeks that my wallet wont get synced ,when i open bitmonerod.exe i see the yellow lines  but i get some errors too for example :

2014-Sep-04 13:41:05.157176 [P2P9]tx with id: <c77b3d378e28325688fe6c134612f74d2
7b87322020a9105da2a80814c24c176> in block id: <873965fc48e5ec7e27d75e6a2c84c3e00
c695a789bc3767aa680886d99adff2b> already in blockchain
2014-Sep-04 13:41:05.163177 [P2P9]Block with id: <873965fc48e5ec7e27d75e6a2c84c3
e00c695a789bc3767aa680886d99adff2b> failed to add transaction to blockchain stor
age
2014-Sep-04 13:41:05.168177 [P2P9][178.221.229.244:17503 INC]Block verification
failed, dropping connection


what i realize that it stocked on block 180790 and it wont go up any more
its been working fine before 2 weeks ago but i dont know y right now not working
my windows is 8.1 64 bit
and i have enough disk space
i deleted p2pstate.bin and poolstate.bin to see if the problem will be solved or not but nothing happend
and one thing more i realized is that although its not syncing but it consumes alot of bandwith
i will be thankful if any one can help me out


Are you sure you are running the 64bit daemon?
Are you sure you have enough RAM+swap?
Are you sure the partition is not FAT32?
superresistant
Legendary
*
Offline Offline

Activity: 2072
Merit: 1097



View Profile
September 04, 2014, 09:34:39 AM
 #12623

why the fuck does mintpal not stop trading?

Mintpal staff is always high on drugs and Mintpal users are even worse because they buy XMR instead of selling.
bagad
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
September 04, 2014, 09:36:15 AM
 #12624

@bagad: have you updated yourr wallet? you are aware that there was a mandatory update a few weeks ago?


i donwload the latest bitmonerod.exe and simplewallet. exe and replaced it with the old one but nothing happened
F22Raptor
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
September 04, 2014, 09:36:45 AM
 #12625

Hi,i'm new to the community and i will study this coin and do what i can do to promote Wink
Quicken
Sr. Member
****
Offline Offline

Activity: 280
Merit: 250


View Profile
September 04, 2014, 09:37:38 AM
 #12626

Hi,i'm new to the community and i will study this coin and do what i can do to promote Wink

Hey, Welcome. You picked a lively day to join.  Smiley
rpietila
Donator
Legendary
*
Offline Offline

Activity: 1722
Merit: 1016



View Profile
September 04, 2014, 09:38:21 AM
 #12627

Now I realize what was the reason for the mid-move turn back at 510 and the quite strong selling towards 400, which was not supported by fundamentals or anything.

The attackers have taken a short position during the decline (causing the decline), and when they run out of coins, the price also stopped declining. When it started going up, it was the time to attack.

Now if the holders sell their coins so that the price drops to below 400, without corresponding buyers except the attackers, then the attackers have won financially, fleecing the community. (The community has also won, because the bug was fixed and attack repelled.)

I pledge 1000 XMR to the devs for their ongoing good work, and BTC100 will be used to buy moneros in the exchange without further warning if I deem that the scamattackers are about to get too fat a profit from their attack.

HIM TVA Dragon, AOK-GM, Emperor of the Earth, Creator of the World, King of Crypto Kingdom, Lord of Malla, AOD-GEN, SA-GEN5, Ministry of Plenty (Join NOW!), Professor of Economics and Theology, Ph.D, AM, Chairman, Treasurer, Founder, CEO, 3*MG-2, 82*OHK, NKP, WTF, FFF, etc(x3)
dasdasdasdasdasd
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
September 04, 2014, 09:41:03 AM
 #12628

https://twitter.com/petertoddbtc/status/507407230204125184

"First time I'm compiling #monero, and its consensus is broken :/ "

HAHAHAHAH RIP MONERO
arielbit
Legendary
*
Offline Offline

Activity: 2310
Merit: 1022


View Profile
September 04, 2014, 09:42:07 AM
 #12629

Blah blah blah i wish i have more btc..a lot of xmr will change hands hehe  Cheesy
fluffypony
Donator
Legendary
*
Offline Offline

Activity: 1274
Merit: 1057


GetMonero.org / MyMonero.com


View Profile WWW
September 04, 2014, 09:42:31 AM
 #12630

https://twitter.com/petertoddbtc/status/507407230204125184

"First time I'm compiling #monero, and its consensus is broken :/ "

HAHAHAHAH RIP MONERO

Followed by: https://twitter.com/petertoddbtc/status/507410029306449920

"It'll be fine in the long run. #Bitcoin's had similar problems in the past after all, e.g. the "make Bitcoins out of thin air" bug."

Nice try, though.

coinweaver
Full Member
***
Offline Offline

Activity: 176
Merit: 100


View Profile
September 04, 2014, 09:43:40 AM
 #12631

Now I realize what was the reason for the mid-move turn back at 510 and the quite strong selling towards 400, which was not supported by fundamentals or anything.

The attackers have taken a short position during the decline (causing the decline), and when they run out of coins, the price also stopped declining. When it started going up, it was the time to attack.

Now if the holders sell their coins so that the price drops to below 400, without corresponding buyers except the attackers, then the attackers have won financially, fleecing the community. (The community has also won, because the bug was fixed and attack repelled.)

I pledge 1000 XMR to the devs for their ongoing good work, and BTC100 will be used to buy moneros in the exchange without further warning if I deem that the scamattackers are about to get too fat a profit from their attack.
Yeah... that's called an "exit pump".
dasdasdasdasdasd
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
September 04, 2014, 09:48:31 AM
 #12632

Now I realize what was the reason for the mid-move turn back at 510 and the quite strong selling towards 400, which was not supported by fundamentals or anything.

The attackers have taken a short position during the decline (causing the decline), and when they run out of coins, the price also stopped declining. When it started going up, it was the time to attack.

Now if the holders sell their coins so that the price drops to below 400, without corresponding buyers except the attackers, then the attackers have won financially, fleecing the community. (The community has also won, because the bug was fixed and attack repelled.)

I pledge 1000 XMR to the devs for their ongoing good work, and BTC100 will be used to buy moneros in the exchange without further warning if I deem that the scamattackers are about to get too fat a profit from their attack.
Yeah... that's called an "exit pump".

WEINER IS HERE SELL SELL SELL SELL
ShroomsKit_Disgrace
Legendary
*
Offline Offline

Activity: 952
Merit: 1000

Yeah! I hate ShroomsKit!


View Profile
September 04, 2014, 09:49:13 AM
 #12633

I think this thread is going to be a troll-party until all this mess is solved (if it can be solved)
superresistant
Legendary
*
Offline Offline

Activity: 2072
Merit: 1097



View Profile
September 04, 2014, 09:56:01 AM
 #12634

I think this thread is going to be a troll-party until all this mess is solved (if it can be solved)

if it can be solved

^ that was trolling
Of course it will be fixed. Bitcoin had many issues like this.
Johnny Mnemonic
Hero Member
*****
Offline Offline

Activity: 794
Merit: 512



View Profile
September 04, 2014, 09:57:25 AM
 #12635

I think this thread is going to be a troll-party until all this mess is solved (if it can be solved)

As your post history indicates, you're the biggest troll here.
JypsiCreme
Full Member
***
Offline Offline

Activity: 149
Merit: 100


View Profile
September 04, 2014, 09:57:49 AM
 #12636

Monero devs took CryptoNote protocol and tried to implement some changes without any understanding of what they're doing. Probably XMR’s devs questionable modifications lead to this kind of attack. That is what you get when you steal the code you are not capable of maintaining.

Remember kids: you should not modify a code if you’re not completely sure what it will cause. Currently people are paying with their funds because of the incompetent Monero devs. Reminds me too much of a real world situation, when the bank closes people loose funds they've invested. I hoped we wouldn't see it in the crypto world.

That's utterly inane - we've made no protocol-level modifications that would cause this. If TFT's original modifications caused this and nobody noticed that has nothing to do with us.

XMR turned out to be the same shit as Quazar just with an instamine scam. Incapable devs that can’t look at the code and placed a critical bug inside it. Fascinating how many people can’t do their work on Monero development right but still have time to post nonsense PR on the forum.
fluffypony
Donator
Legendary
*
Offline Offline

Activity: 1274
Merit: 1057


GetMonero.org / MyMonero.com


View Profile WWW
September 04, 2014, 09:59:59 AM
 #12637

2014/08/04 Attack: Update 1

Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.

Thus the good news is that the consensus code works, and only one fork has survived. The bad news is that those on the bad fork are not reorganising back to the fork, and that is something we will need to look at fixing in future - the consensus code is so aggressive that it refuses to believe that the peers on the "good" fork are correct.

To determine if you are on the good or the bad (dead) fork, you can check "diff" in your daemon window. If you are stuck on 202647 or thereabouts, you will need to delete your blockchain and sync from scratch. I strongly suggest using the blockchain bootstrap downloads from the OP, as those are on the correct fork. Please note that the Windows blockchain bootstrap download has not been checked and updated as yet, I will be doing so in the next few hours, so we have rolled back to a Windows blockchain from a few weeks back. The Linux and OS X blockchain bootstraps are fine.

The next step is to determine how, exactly, 202612 & 202613 managed to cause this, which is what we've been doing concurrently and will continue to do. You can use Monero with caution if you are on the main chain, we will continue to update as we proceed.

NB: no funds have been lost, and there will be no blockchain rollback. If you transacted on the dead fork it was only live for about 35 minutes, so chances are little happened of relevance. Once you are on the good fork you can re-sync your wallets and any funds you sent on the dead fork will reappear.

bigj
Full Member
***
Offline Offline

Activity: 198
Merit: 100



View Profile
September 04, 2014, 10:02:13 AM
 #12638

Now I realize what was the reason for the mid-move turn back at 510 and the quite strong selling towards 400, which was not supported by fundamentals or anything.

The attackers have taken a short position during the decline (causing the decline), and when they run out of coins, the price also stopped declining. When it started going up, it was the time to attack.

Now if the holders sell their coins so that the price drops to below 400, without corresponding buyers except the attackers, then the attackers have won financially, fleecing the community. (The community has also won, because the bug was fixed and attack repelled.)

I pledge 1000 XMR to the devs for their ongoing good work, and BTC100 will be used to buy moneros in the exchange without further warning if I deem that the scamattackers are about to get too fat a profit from their attack.

I will use another ~BTC10 to buy XMR once the time has come (/ trading continues).
jeezy
Legendary
*
Offline Offline

Activity: 1236
Merit: 1010



View Profile
September 04, 2014, 10:03:10 AM
 #12639

2014/08/04 Attack: Update 1

Here's what we've ascertained thus far: the "bad block" occurred at 202612. Immediately thereafter there was 202613, which also has oddities, and then at 202614 the network forked. The "A" part of the network has "c29e3dc37d8da3e72e506e31a213a58771b24450144305bcba9e70fa4d6ea6fb" as the block hash on 202614, the "B" part of the network has "ed4eea6109a1b662cf4a3bb372ed4bdee588160b0ac371c2ad78c5e603b8f2ac" as the block hash on 202614. Ultimately the "A" part won, and is the current fork. The "B" part is dead and has not proceeded beyond block 202647.

Thus the good news is that the consensus code works, and only one fork has survived. The bad news is that those on the bad fork are not reorganising back to the fork, and that is something we will need to look at fixing in future - the consensus code is so aggressive that it refuses to believe that the peers on the "good" fork are correct.

To determine if you are on the good or the bad (dead) fork, you can check "diff" in your daemon window. If you are stuck on 202647 or thereabouts, you will need to delete your blockchain and sync from scratch. I strongly suggest using the blockchain bootstrap downloads from the OP, as those are on the correct fork. Please note that the Windows blockchain bootstrap download has not been checked and updated as yet, I will be doing so in the next few hours, so we have rolled back to a Windows blockchain from a few weeks back. The Linux and OS X blockchain bootstraps are fine.

The next step is to determine how, exactly, 202612 & 202613 managed to cause this, which is what we've been doing concurrently and will continue to do. You can use Monero with caution if you are on the main chain, we will continue to update as we proceed.

NB: no funds have been lost, and there will be no blockchain rollback. If you transacted on the dead fork it was only live for about 35 minutes, so chances are little happened of relevance. Once you are on the good fork you can re-sync your wallets and any funds you sent on the dead fork will reappear.

Thanks for the update. Keep up the good work. Hopefully you will be able to fix the issue in short time.
wonderloops
Full Member
***
Offline Offline

Activity: 228
Merit: 100



View Profile
September 04, 2014, 10:06:14 AM
 #12640

http://da-data.blogspot.com.au/2014/08/minting-money-with-monero-and-cpu.html

Are the claims in this post confirmed FUD?
Pages: « 1 ... 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 [632] 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 ... 2083 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!