plast555
|
|
July 11, 2016, 09:24:27 AM |
|
The main problem is that people lost and loosing a lot of money on mining. Yesterday hash speed felt down to 19 GH/s and that was just 2 pools mining and after we received 110 confirmations someone changed all that blocks, most of them were almost confirmed at c-cex, had more than 100 confirmations, so there were not other hashes except from this 2 pools, so how the heck is that possible !?!
|
|
|
|
|
|
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
yocoin15 (OP)
|
|
July 11, 2016, 01:27:51 PM |
|
NEWS Unfortunately our dev account on c-cex hacked and the hacker stolen 466 Bitcoins and around 1.1 M yocoinStolen Yocoin proof: -1120750 YOC to YjN8azjGeEHSHzjwF23ehvwL1USN3D4Kss (Inner_1468065128W60588B47F02DBC9450C5BD88735) Stolen Bitcoin proof: https://blockchain.info/tx/1b990b73e0699428f4ca0347c0f40569eece66c389c4cd017072dee4d7a08933We should learn from this, we should enable 2fa for the safety. We lost 466 Bitcoins and 1.1 M Yocoins, but don't worry we are still here developing Yocoin, we need your support to make Yocoin Rising. Soon Yocoin would be listed on Bittrex, please help us by joining our slack channel we will announce the procedure soon.
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3444
Merit: 1126
|
|
July 11, 2016, 01:35:34 PM |
|
The main problem is that people lost and loosing a lot of money on mining. Yesterday hash speed felt down to 19 GH/s and that was just 2 pools mining and after we received 110 confirmations someone changed all that blocks, most of them were almost confirmed at c-cex, had more than 100 confirmations, so there were not other hashes except from this 2 pools, so how the heck is that possible !?!
We dropped it cause all the blocks we've been finding turned to orphans for 3-4 days. Waste of hash
|
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
Ducquidhan
Newbie
Offline
Activity: 2
Merit: 0
|
|
July 11, 2016, 03:48:01 PM |
|
HOW MINNING YOC ON GPU AMD WINDOW64..?
|
|
|
|
yocoin15 (OP)
|
|
July 11, 2016, 05:22:15 PM |
|
|
|
|
|
smarterhash
|
|
July 11, 2016, 05:24:06 PM |
|
NEWS Unfortunately our dev account on c-cex hacked and the hacker stolen 466 Bitcoins and around 1.1 M yocoinStolen Yocoin proof: -1120750 YOC to YjN8azjGeEHSHzjwF23ehvwL1USN3D4Kss (Inner_1468065128W60588B47F02DBC9450C5BD88735) Stolen Bitcoin proof: https://blockchain.info/tx/1b990b73e0699428f4ca0347c0f40569eece66c389c4cd017072dee4d7a08933We should learn from this, we should enable 2fa for the safety. We lost 466 Bitcoins and 1.1 M Yocoins, but don't worry we are still here developing Yocoin, we need your support to make Yocoin Rising. Soon Yocoin would be listed on Bittrex, please help us by joining our slack channel we will announce the procedure soon. ever heard of MFA?
|
|
|
|
dolores13
|
|
July 11, 2016, 06:59:07 PM |
|
NEWS Unfortunately our dev account on c-cex hacked and the hacker stolen 466 Bitcoins and around 1.1 M yocoinStolen Yocoin proof: -1120750 YOC to YjN8azjGeEHSHzjwF23ehvwL1USN3D4Kss (Inner_1468065128W60588B47F02DBC9450C5BD88735) Stolen Bitcoin proof: https://blockchain.info/tx/1b990b73e0699428f4ca0347c0f40569eece66c389c4cd017072dee4d7a08933We should learn from this, we should enable 2fa for the safety. We lost 466 Bitcoins and 1.1 M Yocoins, but don't worry we are still here developing Yocoin, we need your support to make Yocoin Rising. Soon Yocoin would be listed on Bittrex, please help us by joining our slack channel we will announce the procedure soon. Nice try Jacko, always the same old story of "dev account was hacked" , but the real question is How the hacker managed to withdraw btc and yoc without access to dev email account to valid withdraw confirmation link.
|
|
|
|
Chris Sokolowski
|
|
July 12, 2016, 01:06:17 AM |
|
The developers control the seed nodes, and the seed nodes are responsible for the orphans. In other words, the developers are likely mining the coin and have rigged the seed nodes to make sure that their blocks are preferentially confirmed. Then, they are selling the blocks on C-CEX and calling it "hacking", If these seed nodes were so flawed, they would be orphaning blocks since the coin's inception, not when the price suddenly rose. I don't expect any fix to come out, since the developers are making a killing so long as the price stays high enough to justify renting hashrate to dominate the network.
|
Prohashing - Professional Mining Made Simple Visit us at https://prohashing.comOptimized for performance - 15 algorithms - Payouts in 200 coins - PPS, PPLNS, or solo
|
|
|
yocoin15 (OP)
|
|
July 12, 2016, 01:33:37 AM |
|
We found The problem that causing Orphan blocks The issue is that we have multiple groups of nodes which are not connected directly. How these orphan blocks appear: - we have groups of nodes A, B, .. Z. Some of the groups have miners. Since the blocktime is preaty small, each group can mine blocks before this data is synced between groups.
Solution: + We need to connect seed nodes between each other. + We need each group have connection to our seed nodes.
There are multiple steps avaialable but let's start from the most simple one.
1. On every node we have, add the following lines to the config file (.conf) It will make the wallet to have permanent connections to these nodes, higher priority that peers.dat addnode=192.52.166.80 addnode=185.122.58.148 addnode=185.122.57.177 addnode=216.189.150.21 addnode=85.25.207.141 addnode=144.76.71.141 addnode=104.131.163.132 addnode=188.134.72.213 addnode=159.203.31.42 addnode=91.134.120.222 addnode=192.241.255.22 addnode=175.192.238.141 addnode=104.172.24.79 addnode=148.251.19.213 addnode=185.122.57.191 addnode=81.133.148.6 addnode=87.203.85.201 addnode=85.214.125.73
2. After the changes are done restart the daemon.
3. In the source code in src/net.cpp you have static const char *strMainNetDNSSeed[][2] = { {"95.211.57.108", "95.211.57.108"}, {"192.52.166.80", "192.52.166.80"}, {NULL, NULL} };
3.1 we should replace IP addresses with domain names Like n1.tekyfaucets.xyz, n2.tekyfaucets.xyz It will allow to change servers withour a need to issue new version of the wallet.
3.2 Extend hardcoded seed nodes to at least 5-7 nodes.
4. Remove all nodes from the recomended list which we don't controll. It's better to extend our own nodes to 5-10 for now.
-------------------
If you can help us to do this please join our slack.
|
|
|
|
yocoin15 (OP)
|
|
July 12, 2016, 04:59:23 AM |
|
ANNOUNCEMENT All Yocoin holders / miners / community members and service providers are requested to make sure that their wallets are connected with official fork. Members who are having issues with the unconfirmed transactions are requested to delete their blockchain or backup all files and resync their wallets with correct configuration. (process explained below) Please note, it is user responsibility to backup their data files Yocoin team will not be responsible for any loss which you might face due to any improperly taken backup or deleted data files. Generic paths where Yocoin data files will be stored at following path: Windows XP C:\Documents and Settings\<username>\Application Data\Yocoin-YOC\ Windows Vista, 7 %appdata%/Yocoin-YOC/ Linux /home/<username>/.Yocoin-YOC/ Mac OSX /Users/<username>/Library/Application Support/Yocoin-YOC/ Step 1: Close your wallet / Yocoin Clients Step 2: You are requested to backup all files from aforementioned folder to some different location in your system; however you need to leave a copy of wallet.dat file in same folder. Step 3: Create a new file Yocoin.conf with following details in it: Dont forget to change your username & password in below configuration listen=1 server=1 daemon=1 rpcuser=username rpcpassword=password rpcport=30307 port=30308 addnode=192.52.166.80 addnode=185.122.58.148 addnode=185.122.57.177 addnode=216.189.150.21 Step 4: After saving above file open/start your wallets and wait it to sync with network. Step 5: Once your wallets will be sync properly make sure you are on official fork by matching your block height with our: explorer http://explorer.yocoin.org crawler http://185.122.58.148/index.phpThis solution had been tested and verified by various community members on all yocoin services and at the moment best option to overcome on ORPHAN blocks issue. Please note: We have removed C-CEX maintained node list from the main post since we have no control on the nodes listed init, except our official ones. We (YoCoin Team) apologize you for any inconvenience which you had faced during past week and request you to hold your miners until orphan blocks / fork issue will get resolved and verified by all of you guys.
|
|
|
|
cryptofarmer
|
|
July 12, 2016, 08:32:45 AM |
|
Still getting Orphanes. Here's what the block explorer shows, notice the double blocks. 47962 128979cb6cbdd1b584d052e4e9ddb19d246ce76a952587db062b6eec876127d8 1 50.00000000 Tue, 12 Jul 2016 08:29:29 GMT 47961 e2d9a034c21da617743f897812e4459caa2754d5e22dd4e1d9bb8722579805fa 1 50.00000000 Tue, 12 Jul 2016 08:28:49 GMT 47960 67b9070fca6dbdc932dde94ad4e31a6544e4513240bfbd454be21d07e7adbe8f 1 50.00000000 Tue, 12 Jul 2016 08:28:07 GMT 47960 8409c9a8f40d7f93ee1902cee2f487dd3e341acb868fa845b0d0a5d89cc08cd8 1 50.00000000 Tue, 12 Jul 2016 08:27:09 GMT 47959 faa02fa86d174124cc9bb58fbb2173931343b67ce60e16da9d67a93943cea3b1 1 50.00000000 Tue, 12 Jul 2016 08:26:24 GMT 47958 8b420e3016c7b353e3e924505e8bbe4cafe0e5f3269db1b8fad5e76964bf25ae 2 97.00000000 Tue, 12 Jul 2016 08:24:24 GMT 47958 94da5d84eaa946e766f7e4ad068c4256766c33f03be033626e7fd79fb1ae677a 1 50.00000000 Tue, 12 Jul 2016 08:24:24 GMT 47957 52cd6703705e60f38f6472b4eff230caced64041cc87e694d59d10dff57164c8 2 200.09624000 Tue, 12 Jul 2016 08:21:22 GMT 47957 e8155c3dca6102ad77167dcae8d0f02f32f182b975692cda3e02c87b8f086d54 1 50.00001000 Tue, 12 Jul 2016 08:21:22 GMT 47956 915b5498ffe367f4acea2a3dff9286bcdf85e5bbd001374769412ae8005b7f23 1 50.00000000 Tue, 12 Jul 2016 08:20:53 GMT ANNOUNCEMENT All Yocoin holders / miners / community members and service providers are requested to make sure that their wallets are connected with official fork. Members who are having issues with the unconfirmed transactions are requested to delete their blockchain or backup all files and resync their wallets with correct configuration. (process explained below) Please note, it is user responsibility to backup their data files Yocoin team will not be responsible for any loss which you might face due to any improperly taken backup or deleted data files. Generic paths where Yocoin data files will be stored at following path: Windows XP C:\Documents and Settings\<username>\Application Data\Yocoin-YOC\ Windows Vista, 7 %appdata%/Yocoin-YOC/ Linux /home/<username>/.Yocoin-YOC/ Mac OSX /Users/<username>/Library/Application Support/Yocoin-YOC/ Step 1: Close your wallet / Yocoin Clients Step 2: You are requested to backup all files from aforementioned folder to some different location in your system; however you need to leave a copy of wallet.dat file in same folder. Step 3: Create a new file Yocoin.conf with following details in it: Dont forget to change your username & password in below configuration listen=1 server=1 daemon=1 rpcuser=username rpcpassword=password rpcport=30307 port=30308 addnode=192.52.166.80 addnode=185.122.58.148 addnode=185.122.57.177 addnode=216.189.150.21 Step 4: After saving above file open/start your wallets and wait it to sync with network. Step 5: Once your wallets will be sync properly make sure you are on official fork by matching your block height with our: explorer http://explorer.yocoin.org crawler http://185.122.58.148/index.phpThis solution had been tested and verified by various community members on all yocoin services and at the moment best option to overcome on ORPHAN blocks issue. Please note: We have removed C-CEX maintained node list from the main post since we have no control on the nodes listed init, except our official ones. We (YoCoin Team) apologize you for any inconvenience which you had faced during past week and request you to hold your miners until orphan blocks / fork issue will get resolved and verified by all of you guys.
|
|
|
|
gambino
|
|
July 12, 2016, 10:06:46 AM Last edit: July 12, 2016, 11:09:51 AM by gambino |
|
By now the dev is getting all the blocks because he made some glitch with the seed nodes As we know the IRC of the wallet is working well and everyone got more than 20 active connections, so the dev can easy turn off the buggy seednodes, but he is not going to do that as he get every block. If i'm wrong how the hell every pool got only orphans, even the official? I'm mining on solo (with the wallet which shows 11 ?FALSE? positive on virus scan) and guess what - ONLY ORPHANS After i hit a block it shows in both block explorers! Few minutes after that the coins became orphan in my wallet, but they stay in the block explorer. http://explorer.yocoin.org/tx/e87db1df90bd8a048f455a8fddef8447132515c3e5e78023c87d937eb1dc5a9elisttransactions [ { "account" : "", "address" : "YeoY7vPAt6fsca6xA55xHa1Bs5fZSdbJhB", "category" : "orphan", "amount" : 50.00001000, "confirmations" : 0, "generated" : true, "txid" : "e87db1df90bd8a048f455a8fddef8447132515c3e5e78023c87d937eb1dc5a9e", "time" : 1468319505, "timereceived" : 1468319528 }, { "account" : "", "address" : "YfnkiJMZzT4DNqsWQhAAjZhQmXFbBubkiL", "category" : "orphan", "amount" : 50.00000000, "confirmations" : 0, "generated" : true, "txid" : "72d40eea256941ca82a942025b29e197bf6f5c00187f1ec80ef3167de36bb325", "time" : 1468319858, "timereceived" : 1468319898 }, { "account" : "", "address" : "YQmPvbnKxUH1ZnPNPnL3xHVWVQP35F1ngv", "category" : "orphan", "amount" : 50.00000000, "confirmations" : 0, "generated" : true, "txid" : "548fea18c1b082dc2e185201fc87321c32e3503117a458a206d5ea58876dd164", "time" : 1468320175, "timereceived" : 1468320221 } ]
Please check the txid on the block explorer! They are there! With the same addresses! Maybe is time for big red letters PS Unfortunately our dev account on c-cex hacked and the hacker stolen 466 Bitcoins and around 1.1 M yocoin if this is true, i will call it karma
|
|
|
|
gambino
|
|
July 12, 2016, 11:42:01 AM Last edit: July 12, 2016, 11:57:40 AM by gambino |
|
AVOID THIS COPY PASTED PUMP&DUMP SHITCOIN WHICH HAVE HUGE PREMINE AND ALL NEWLY GENERATED BLOCKS ARE GOING TO DEV'S POCKET ALSO WINDOWS WALLET HAVE 11 VIRUS ALERTS
|
|
|
|
Peltig
Full Member
Offline
Activity: 126
Merit: 100
★YoBit.Net★ 350+ Coins Exchange & Dice
|
|
July 12, 2016, 01:02:52 PM |
|
Which pools are active & they are connected to exchanges?
|
|
|
|
smarterhash
|
|
July 12, 2016, 01:08:29 PM |
|
Which pools are active & they are connected to exchanges?
all blocks are being orphaned and stolen - there's no use in mining.
|
|
|
|
dutch_loneranger
|
|
July 12, 2016, 02:59:35 PM |
|
i was a first miner and didnt see the swap . so i was late now i see they had million yocoin that is stolen en lots of btc. for me it was only 699 yocoin that needed too be swap . and a few also contacted me if i got my coins . and they had more . and now i see they had a million. so the few that asked had easily could get it . glad that i sold the one that i had empeox. how can a dev. not really work on a fix . or be more active too explain. it almost look like paycoin.
big words big advertisement but big scam
|
|
|
|
siri1972
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 12, 2016, 03:31:53 PM |
|
@dutch_loneranger do u received the weekly coins from yocoin company
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3444
Merit: 1126
|
|
July 12, 2016, 03:53:43 PM |
|
We found The problem that causing Orphan blocks The issue is that we have multiple groups of nodes which are not connected directly. How these orphan blocks appear: - we have groups of nodes A, B, .. Z. Some of the groups have miners. Since the blocktime is preaty small, each group can mine blocks before this data is synced between groups.
Solution: + We need to connect seed nodes between each other. + We need each group have connection to our seed nodes.
There are multiple steps avaialable but let's start from the most simple one.
1. On every node we have, add the following lines to the config file (.conf) It will make the wallet to have permanent connections to these nodes, higher priority that peers.dat addnode=192.52.166.80 addnode=185.122.58.148 addnode=185.122.57.177 addnode=216.189.150.21 addnode=85.25.207.141 addnode=144.76.71.141 addnode=104.131.163.132 addnode=188.134.72.213 addnode=159.203.31.42 addnode=91.134.120.222 addnode=192.241.255.22 addnode=175.192.238.141 addnode=104.172.24.79 addnode=148.251.19.213 addnode=185.122.57.191 addnode=81.133.148.6 addnode=87.203.85.201 addnode=85.214.125.73
2. After the changes are done restart the daemon.
3. In the source code in src/net.cpp you have static const char *strMainNetDNSSeed[][2] = { {"95.211.57.108", "95.211.57.108"}, {"192.52.166.80", "192.52.166.80"}, {NULL, NULL} };
3.1 we should replace IP addresses with domain names Like n1.tekyfaucets.xyz, n2.tekyfaucets.xyz It will allow to change servers withour a need to issue new version of the wallet.
3.2 Extend hardcoded seed nodes to at least 5-7 nodes.
4. Remove all nodes from the recomended list which we don't controll. It's better to extend our own nodes to 5-10 for now.
-------------------
If you can help us to do this please join our slack.shit still orphans
|
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
smarterhash
|
|
July 12, 2016, 04:31:14 PM |
|
We found The problem that causing Orphan blocks The issue is that we have multiple groups of nodes which are not connected directly. How these orphan blocks appear: - we have groups of nodes A, B, .. Z. Some of the groups have miners. Since the blocktime is preaty small, each group can mine blocks before this data is synced between groups.
Solution: + We need to connect seed nodes between each other. + We need each group have connection to our seed nodes.
There are multiple steps avaialable but let's start from the most simple one.
1. On every node we have, add the following lines to the config file (.conf) It will make the wallet to have permanent connections to these nodes, higher priority that peers.dat addnode=192.52.166.80 addnode=185.122.58.148 addnode=185.122.57.177 addnode=216.189.150.21 addnode=85.25.207.141 addnode=144.76.71.141 addnode=104.131.163.132 addnode=188.134.72.213 addnode=159.203.31.42 addnode=91.134.120.222 addnode=192.241.255.22 addnode=175.192.238.141 addnode=104.172.24.79 addnode=148.251.19.213 addnode=185.122.57.191 addnode=81.133.148.6 addnode=87.203.85.201 addnode=85.214.125.73
2. After the changes are done restart the daemon.
3. In the source code in src/net.cpp you have static const char *strMainNetDNSSeed[][2] = { {"95.211.57.108", "95.211.57.108"}, {"192.52.166.80", "192.52.166.80"}, {NULL, NULL} };
3.1 we should replace IP addresses with domain names Like n1.tekyfaucets.xyz, n2.tekyfaucets.xyz It will allow to change servers withour a need to issue new version of the wallet.
3.2 Extend hardcoded seed nodes to at least 5-7 nodes.
4. Remove all nodes from the recomended list which we don't controll. It's better to extend our own nodes to 5-10 for now.
-------------------
If you can help us to do this please join our slack.shit still orphans ditto - there's an infected node in the list
|
|
|
|
sxafir
|
|
July 12, 2016, 04:43:13 PM |
|
In my Phone node 81.133..... is Mark Blue maybe this is infected.
|
|
|
|
|