|
542
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] AEON [2017-04-23: update to 0.9.12.0]
|
on: August 31, 2017, 08:10:50 AM
|
AEON is not profitable for mining since May.
I have a Ryzen 1700@3650, and have 2,2 Kh... with 50ºc (ambient 35º) 15 low priority/threads with minor performance penalty and 80 W. CPU package power (HWiNFO64). I think AEON it's a very good profitable CPU miner coin. Ok, I will try to make myself clear. I can mine AEON with my hardware and profitabitily margin is about 24 AEON per day. If I mine more - it's profitable. If less - Monero is more profitable, I can mine Monero, sell it, buy AEON and have more amount comparing direct mining. In May I had 120 coins per day, mining was 2-3 times more profitable than Monero. In August I had 12-15 AEON so monero mining gave me 2x more. |
|
|
|
|
543
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] AEON [2017-04-23: update to 0.9.12.0]
|
on: August 31, 2017, 08:03:13 AM
|
Original AEON was forked from Monero.
Why we couldn't take fresh Monero release and fork it again - the same way as it was done initially?
What do you mean? Restart everything from scratch again? I reckon that it would present more problems and complications. The first problem that comes to mind are the amounts in the wallets. Nope. You don't have to start from scratch but use existing blockchain instead. |
|
|
|
|
548
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BCN] Bytecoin. Secure, private, untraceable since 2012
|
on: August 30, 2017, 11:14:35 AM
|
Dear community,
As far as we received some messages about a dev team in this thread I have to make the situation clear.
Earlier I used to write that we’re the team of 4 full-time developers, freelance devs, cryptography expert a and a community manager . There’s no “old” or “new” team at all, it’s not a relationships where you can have a lot of “ex” and “present”. Bytecoin has a straight vector of development and none of those “old” and “new” once can change it. To calm those of you who are still wondering about the team: we do cooperate with all of the previous devs and the main ones of them are still with us at a main cast. There’s nothing to worry about.
Speaking about today’s temps of developing. Are those regular updates, releases and total quality of the project don’t prove the professional skills we have? Please, don’t spread the panic, we’re working every damn day to make BCN better than yesterday. And the results of the last two months are reflecting our efforts.
OK, no problem. Just show us a succession and continuity. The one message only from any of old team members and I will trust you and your words. There is a list of original team members - https://bytecoin.org/teto-team/Who are you in this list, show us your nickname. And tell who is still onboard from this guys. |
|
|
|
|
552
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [DSH] Dashcoin (Cryptonote) UPDATE: New source/wallets+GUI - 1.0.10
|
on: August 28, 2017, 10:24:41 AM
|
Can someone provide some peers?
Anyone knows the peer address from the pools? IP and port?
Can't sync
78.47.184.165:29080 80.12.85.56:29080 138.201.116.10:29080 185.16.220.3:29080 45.32.69.211:29080 45.76.34.101:7610 37.9.28.39:29080 176.9.47.243:7280 Thanks, I've added the lines to config: add-peer=xxxxx with the ones you provided, but didn't solve it 2017-Aug-27 23:43:55.170037 ERROR [185.16.220.3:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:43:55.174042 WARNING Failed to HANDSHAKE with peer 185.16.220.3:29080
2017-Aug-27 23:43:55.296194 ERROR [176.9.47.243:7280 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:43:55.299699 WARNING Failed to HANDSHAKE with peer 176.9.47.243:7280
2017-Aug-27 23:43:58.061147 ERROR [45.76.34.101:7610 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:43:58.064651 WARNING Failed to HANDSHAKE with peer 45.76.34.101:7610
2017-Aug-27 23:44:04.565268 ERROR [37.9.28.39:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:04.569274 WARNING Failed to HANDSHAKE with peer 37.9.28.39:29080
2017-Aug-27 23:44:10.152745 ERROR [78.47.184.165:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:10.156250 WARNING Failed to HANDSHAKE with peer 78.47.184.165:29080
2017-Aug-27 23:44:12.283406 ERROR [176.9.47.243:7280 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:12.287411 WARNING Failed to HANDSHAKE with peer 176.9.47.243:7280
2017-Aug-27 23:44:15.104929 ERROR [45.76.34.101:7610 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:15.108433 WARNING Failed to HANDSHAKE with peer 45.76.34.101:7610
2017-Aug-27 23:44:20.779514 ERROR [37.9.28.39:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:20.783019 WARNING Failed to HANDSHAKE with peer 37.9.28.39:29080
2017-Aug-27 23:44:25.880884 ERROR [78.47.184.165:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:25.884890 WARNING Failed to HANDSHAKE with peer 78.47.184.165:29080
2017-Aug-27 23:44:29.429816 ERROR [185.16.220.3:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:29.433320 WARNING Failed to HANDSHAKE with peer 185.16.220.3:29080
2017-Aug-27 23:44:31.566484 ERROR [176.9.47.243:7280 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:31.569988 WARNING Failed to HANDSHAKE with peer 176.9.47.243:7280
2017-Aug-27 23:44:34.269859 ERROR [45.76.34.101:7610 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:34.273864 WARNING Failed to HANDSHAKE with peer 45.76.34.101:7610
2017-Aug-27 23:44:39.457337 ERROR [78.47.184.165:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:39.461342 WARNING Failed to HANDSHAKE with peer 78.47.184.165:29080
2017-Aug-27 23:44:44.182237 ERROR [185.16.220.3:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:44.214777 WARNING Failed to HANDSHAKE with peer 185.16.220.3:29080
2017-Aug-27 23:44:52.004504 ERROR [37.9.28.39:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:44:52.008008 WARNING Failed to HANDSHAKE with peer 37.9.28.39:29080
2017-Aug-27 23:45:02.309371 ERROR [78.47.184.165:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:45:02.313376 WARNING Failed to HANDSHAKE with peer 78.47.184.165:29080
2017-Aug-27 23:45:08.613243 ERROR [37.9.28.39:29080 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:45:08.617248 WARNING Failed to HANDSHAKE with peer 37.9.28.39:29080
2017-Aug-27 23:45:15.579442 ERROR [45.76.34.101:7610 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:45:15.582445 WARNING Failed to HANDSHAKE with peer 45.76.34.101:7610
2017-Aug-27 23:45:15.703096 ERROR [176.9.47.243:7280 OUT] Failed to invoke COMMAND_HANDSHAKE, closing connection.
2017-Aug-27 23:45:15.706600 WARNING Failed to HANDSHAKE with peer 176.9.47.243:7280
Add all list of nodes to your config file: seed-node=108.61.188.93:7610 seed-node=128.199.146.243:29080 seed-node=195.154.181.121:7280 seed-node=93.77.229.33:29080 seed-node=144.76.59.211:29080 seed-node=176.9.147.178:7280 seed-node=176.9.47.243:7280 seed-node=84.200.76.33:29080 seed-node=98.115.76.178:29080 seed-node=195.154.181.121:7280 |
|
|
|
|
553
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BCN] Bytecoin. Secure, private, untraceable since 2012
|
on: August 27, 2017, 06:26:36 PM
|
I checked your reputation, and found that there was a "trust", given by "Ullo" to you a few years ago. Was he the original developer of the bytecoin?
As there is no confirmation from Ullo, DStrange, Wanesst, this may mean that they may have left the team. If they spoke good English, and now there is no official communication directly with the developers on the public forums, this may also mean, the current english speaking part of the team may now include one or two persons, and since some of them were from Russia, it may be the team consists of a few Russia's guys, so without any good English language proficiency, and so no public communication on the public forums. This is not accuse anyone, simple to indicate a possibility. So, these are assumptions of course, and thus can be wrong, but because of no response of the BCN representative to your request, the whole situtation begins to look very strange more and more.
I doubt that their website has been hijacked, and that the BCN representative is thus a fake one. I think it is a real person, however, most probably outsourced anonimously, not knowing and thus not clear about the origins of the bytecoin.
Since you are a Minergate forum moderator, you think it is possible that the Minergate can also delist the bytecoin, if there is no "huge refutation" given very soon?
1. No, Ullo was PR-manager (speaking head of team). 2. Relax dude, I speak Russian fluently  3. MG will not delist BCN - owners and admins too lazy. |
|
|
|
|
Show Posts
