Having multiple socket failures on daemon both recent versions, is this a problem on my end??
2017-Apr-03 07:34:33.731541 [P2P8][sock 13] Some problems at write: Broken pipe:32
2017-Apr-03 08:37:01.913991 [P2P3][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:40:18.924091 [P2P7][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:43:20.505536 [P2P1][sock 16] Some problems at write: Broken pipe:32
2017-Apr-03 08:46:29.252562 [P2P7][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:49:32.701434 [P2P3][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:52:39.518486 [P2P2][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:55:49.193804 [P2P9][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 08:56:20.726422 [P2P4][sock 15] Some problems at write: Connection reset by peer:104
2017-Apr-03 08:59:18.646990 [P2P4][sock 15] Some problems at write: Broken pipe:32
2017-Apr-03 09:00:33.005134 [P2P8][sock 15] Some problems at write: Connection reset by peer:104
.....and many more!!!
seeing many more than usual to the point that wallet RPC failed
Strange. I have tested the wallet quite a bit and I haven't had any problems with it, but others report various issues. Is this Windows or Linux? The broken pipe/connection reset issues are unclear, could be peers not responding (normal) or something else. Can you try rebuilding HEAD from master on my repo and let me know if any different. I have a couple of minor fixes there. https://github.com/iamsmooth/aeon |
|
|
|
building on ubuntu or in a virtual machine running ubuntu is not hard. I think all you need to do is: apt-get install build-essential cmake libboost-all-dev 1git clone https://github.com/aeonix/aeoncd aeon git checkout v0.9.9.0 2make cd build/release/src ./aeond 1 If you are using Ubuntu 14.04 you will need libboost1.55-all-dev (default boost version has a bug and should not be used) 2 Replace with current release tag |
|
|
|
@thefix Your hardware is entirely adequate. At the moment all that is needed is 1 core and 8GB+ of RAM. The important thing when setting it up is to make sure you: 1) compile for low memory mode, and 2) remove all unnecessary plugins especially account_history. If you don't do that memory usage is much higher. As far as another account that is a matter of preference. Some people use their regular account. I prefer not to have any of my regular account keys hot (witness needs a hot signing key to sign blocks and most use a feed script to automatically update the STEEM price feed, in which case you need a hot active key as well). Hmmm, tried to register but it keeps saying my phone number cannot be confirmed...
Try a different phone number or you can PM me. I give free accounts to ranked-up bitcointalk members (without phone number) |
|
|
|
|
The Windows build problem is a known issue. Arux is working on it.
|
|
|
|
As far as I can tell that is from 23 days ago, shortly after the chain problem and before the wallet was brought back up recently. I don't see anything wrong with the transactions on the chain. I would check with bittrex support and see if there is a reason their system didn't credit you. They can check with me if they are having trouble with the wallet, but as far as I can tell it should be there. |
|
|
|
cryptopia shutting down due to rollback? what happend?  We fixed a forking bug, and they called it a "rollback" though it really wasn't that in the sense of someone deciding to reverse anything. To be fairm fixing the bug took quite a while and during that time a lot of blocks got mined onto an invalid chain. Nevertheless, only a few transactions ended up breaking (most worked fine on both the good and bad chains). I think cryptopia's issue had something to do with their database being unable to handle the long reorg that occurred once the bug was fixed. Perhaps they'll have some way to address it going forward and can reenable the coin. We would welcome their support. |
|
|
|
Windows binaries???
Not available YET. We do expect to have them soon. |
|
|
|
New maintenance updateThis maintenance release is highly recommended for all AEON users. Includes reliability and stability fixes Updates embedded miniupupc with latest upstream fixes Resolves build issues with newer compiler/platform versions (some from Monero upstream) Thanks to team member Arux for resolving a number of outstanding build issues for this release. https://github.com/aeonix/aeon/releases/tag/v0.9.9.0
|
|
|
|
Original (also one quoting reply) deleted for use of red. However, I will quote full size and answer the question.
Discussing CK for the time being seems okay given the recent connection with XMR as well as the continuing XMR gateway in the game. In the future if the game diverges too much from XMR it may become off topic but for now it is allowed.
Moderator smooth, is it ok to talk CK in here or not?
|
|
|
|
Looking at the BCN pump in awe, y'all gonna be rollin in $$$ in due course.
Be responsible AEON'ers. With great wealth comes great AEONsibility.
Aeon isn't on Polo so there will be no pump. We do have a disabled wallet like BCN though  |
|
|
|
|
Some people have reported that "stuck at 400" bug but I have no idea how to reproduce it. I've synced countless nodes and never seen it. I do see a short pause at 400 because blocks are processed in groups of 200 and at that point in the chain blocks were fairly large.
Also, if someone is running a pool, please join IRC (or if there is a slack with an IRC gateway that is okay) and try to connect with me. I'd like to test a release candidate with pool mining before pushing it out.
|
|
|
|
|
HODL liquidation update
1 CK per S-HODL share was paid in dividends (about 60000 CK units distributed), leaving 0.7 CK per S-HODL share. Rather than proceed with SPOILing shares as has been done for other such liquidations, I think I will leave things as they are for now. The other remaining assets will continue to pay dividends which can be used (and has been used) to buy more CK units, reducing the disparity. Other developments could occur as well.
Once the remanning assets are resolved if there is still a need to SPOIL some S-HODL shares to complete the distribution then we will do that.
|
|
|
|
|
HODL liquidating
As it appears there will no longer be CK dividends, the need for the HODL fund no longer exists and the fund will liquidate. The existing holdings of CK (about 1.5 CK per S-HODL) will be dividended (and/or sold and used to buy back S-HODL shares from the market, at the option of the manager) and whatever is received from other HODL-held assets (such as the remaining holdings of S-CKG/CKGE which are slowly being liquidated) will also be dividended or used to buy back.
If at some point in the future there is a renewed need for such a fund we can consider creating a new one.
|
|
|
|
|
@rdnkjdi you can see the loan rates on the Lending tab. Each coin has different rates.
|
|
|
|
And many many people lost a fuckload of money because fluffy was telling everybody how bad dash is, right before it sprung x10. These people shorted dash because they beliefed fluffy, and lost all, these shorters are the ones which made the dash price rise exponential bigger than it would have been without the shorting. And they shorted because dash is so bad and its just a pump and dump scam coin and so on, at least everybody told them so - for them 20 dollar a dash was hardly overpriced, look where dash is now.
If you ask for who was scammed by dash, you won't find one (at least noone who was buying in the last 3 years), because price went from ath to ath, there could no one be scammed per definition, because noone could have lost with ath after ath. (for me a scam is if someone loses money! - ofc thats my definition, but its true!). On the other hand lots and lots of people lost money because they shorted dash after all that "its a total scam coin" definition from fluffy and his friends with all these cool videos...
This man speaks the truth. Just keep on listening to Fulffy and Icebreaker and Smooth and Generalthis and who else if you want to keep on losing money. Their track record so far certainly indicates that. Hey wait a minute. I never told anyone to short anything and fluffypony never did either (not sure about the others). I even pointed out on the Dash thread years ago that I own some, and still do, though I wouldn't call it a massive position. I do think long term Dash is going to (nearly) zero, and it won't be alone among today's major cryptos, but that is hardly a reason to short, unless you are prepared to maintain collateral and pay interest (and hope that the shorting market still exists) indefinitely. I'm not recommending that one bit and I never did. As far as the previous quote, this is certainly not correct. Dash has made new ATHs (as had XMR) but that doesn't mean that people didn't lose money, FOMO buying and then selling lower when the hype faded (or other similarly bad trading). Many have. |
|
|
|
|
@6436346346
Good to hear, thanks for the update!
|
|
|
|
Is that an official message from Cryptopia? This has me worried because Bittrex might do the same thing. I just bought my first Aeons which are stuck on Bittrex and I am still syncing my wallet. Would anyone here advice that I should hold bitcoins for now and wait until everything is ok?
I'm in touch with bittrex. They are just waiting for me to finalize the next update, which should be very soon. Cryptopia is being quite bratty IMO. There is a huge difference between doing a rollback as a matter of policy because you want to decide who gets to keep the coins, and releasing a new version of the code that fixes a data store corruption bug. In fact very few transactions were broken anyway; nearly all were confirmed on both the bad and good chains. But it is their exchange and their decision what coins to support. I would also want to know how many nodes there are in the network. Thank you.
It is impossible to know exactly how many nodes there are, but I can say that right now one of my nodes has 19 connections and has seen 341 different nodes "recently" (I cleared peer list not too long ago and that is the whitelist size, meaning successful connections). |
|
|
|
@smooth. I stopped syncing upon reading your post. Do we have to wait for another release update before doing anything? I really want to withdraw from Bittrex now.
I also read the roadmap. How far on the roadmap are we?
You can keep syncing. The problem that I thought I saw was actually an unupgraded node that was aggressively hitting my own node and didn't get banned. I fixed the missing ban case added some extra checks in my development version that I will push soon but what is released now is still okay to use for syncing (next update won't require a resync). As far as the roadmap, lets get past the current issues and then come back to it. |
|
|
|
Here's a reminder of the current system we've come up with for managing this in/out of the game: - Create a CKGAME token in Counterparty with a number equivalent to the amount of CK in Crypto Kingdom (10,496,263).
- Appoint a depository manager in Crypto Kingdom who will hold a Counterparty account that contains all the CKGAME tokens.
- If a withdraw is requested, the player sends CK to the CKGAME account. At that point, the manager will withdraw the CKGAME token in Counterparty to the address provided.
- If a deposit is initiated, the manager will receive a deposit of CKGAME to their address and then verify with the player. Once verification is complete, the manager will GIVE CK [quantity] [player id].
- Dividends continue to work exactly the same. However, any CK -> CKGAME tokens that have been withdrawn will not be able to vote on CK matters or collect a dividend. Any CK held by the CKGAME account will receive a dividend which will then be used to buy CK on the Crypto Kingdom market. This CK will be given to the CKBURN account in-game, and the corresponding amount of CKGAME Counterparty token will be sent to the xcp burn address (1CKGAMEBURNiTALLxxxxxxxxxxxxeLDrH)
This procedure disadvantages CKGAME holders and will discourage investment by those who don't want to join the game (it will also discourage game players from holding on-blockchain or on-exchange CKGAME tokens, reducing its prospects for gaining legitimacy and liquidity) Those who hold CK in-game will receive both the dividend, and also benefit from the price increase from buy-and-burn. Those who hold CKGAME will only benefit from the price increase. For this procedure to work, and not disadvantage CKGAME token holders as welcome passive investors (contributing to the asset value), all dividends paid to CK under the current rules should be redirected to the CKBURN account. The custodian uses those funds to buy CK in-game (leaving them in the CKBURN account, from which the rules would prohibit any other transactions). The corresponding CKGAME tokens would be sent to the XCP burn address as above. Alternately there would need to be two classes of CK (one dividend paying, one not) which would not maintain price parity (as currently with CK and HODL) |
|
|
|
|
Show Posts
