It took a little breather last night, but it seems like it's on again. Anyway, it's not selling that aggressively (approximately 5 XMR per minute) so I don't mind. Rather this than those large dumps. 5 XMR per minute if continuous is a pretty good clip. That's more than half of the mining rate. |
|
|
|
I think it's perfectly reasonable to assume that the founders of the coin had fair distribution as the core value of the coin, and that one exchange taking control of a vast amount of users' coins would not be considered fair distribution.
It isn't plausible this wasn't understood when the coin was created. The existence of parties such as exchanges and others with large numbers of addresses is no secret. |
|
|
|
@smooth & americanpegasus: Pruning FAQ
Q: How does pruning affect functionality?
A: The only inherent functional limitation of AEON's pruning is the inability to restore (also known as rescan) a wallet which was used for spending transactions. All other functionality including sending and receiving coins, mining, updating a wallet after any period of inactivity, cold storage, mining, etc. remain fully supported.
I think this part may no longer be correct. I implemented a work-around for the issue, meaning that even old wallets should sync correctly even against a pruned node. Has anyone tested this and can report either way? Arux tested this and confirmed that the limitation is still there. I had implemented a partial workaround (for cold storage or inactive wallets) but it does not apply if the wallet was actively used for spending. |
|
|
|
...
Pretty much the same except his opinion is listened to by many, many more people than yours (or mine).
Yes, and he didn't say anything negative about Dash. He also said "Dash is pretty innovative" but you didn't hear that, did you? What did he say right after saying that Dash is trying to be innovative? |
|
|
|
@smooth & americanpegasus: Pruning FAQ
Q: How does pruning affect functionality?
A: The only inherent functional limitation of AEON's pruning is the inability to restore (also known as rescan) a wallet which was used for spending transactions. All other functionality including sending and receiving coins, mining, updating a wallet after any period of inactivity, cold storage, mining, etc. remain fully supported.
I think this part may no longer be correct. I implemented a work-around for the issue, meaning that even old wallets should sync correctly even against a pruned node. Has anyone tested this and can report either way? |
|
|
|
|
Congratulations everyone. AEON has gotten large enough to attract its first troll.
|
|
|
|
Even down to 32px I can still clearly tell what it is. At 16px it becomes distorted, but I think you're going to have that effect with any logo. I did some analysis and didn't find any mathematical puns hidden in the logo, though the ratio of the word "aeon" to the rest of the logo is 4:27 which is also considered "international munchie time" (hardy-har-har).
I'm not sure why 16 px is needed, but perhaps a tweaked version could be created that is recognizable by shape even if not readable (mostly: brighten up the white a bit). As far as mathematical puns, if we want them they can get inserted in the sort of "tweak" redesign I suggested, along with slightly changing the font, layout, etc. Ideally if inserted they should be left as undisclosed easter eggs for the curious to find later. |
|
|
|
Charlie Lee (who, whatever you think of Litecoin, is well known and influential) was talking about how the instamine holds Dash back But it doesn't 'hold it back'. Argue it with Charlie Lee, not me. He does how many speaking engagements a year? I do...somewhat less. It is certainly relevant when someone of that visibility states it to be the case, whether you agree with him or not. |
|
|
|
Actually I'm going to say I really like the square blue logo. Looked at against the peer group of professional logos, it holds up well. It's somewhat outside of typical for coin logos, which tend to be overly designed and use too many odd colors and shadings imo. Take a look at the designs posted on the last page or two of this thread and compared with the top-tier corporate logos that Pegasus posted. Our logo fits in better in the latter group, which is a good thing. I don't really care if the original developer banged it out in 15 minutes. Maybe he was a genius, or got lucky. The Tribune, Weather Channel, and even this version of Facebook (not shown in the post above but widely used) are very similar in style and probably cost a fortune (also some others of the "red" persuasion).  What I would suggest is maybe tweaking the font or something if the design is seen as too ordinary. Someone mentioned that is uses a Windows default font. I don't know if that is true but if so we could perhaps find a variation that is a bit more distinctive while keeping the same theme. Also, the logo and currency symbol have nothing to do with each other. The currency symbol could be used as part of the logo but it doesn't have to be. The logo certainly should not be used directly as a currency symbol. |
|
|
|
The offensive language and behavior in the thread has gotten out of hand, however.
Apologize for the use of offensive language. It is just my normal style of writing and was not intended to offend anyone, but now that I have been asked to avoid it on this thread I will abide. |
|
|
|
Gold has been digitized. Everything's been digitized
Not really. A gold-linked or gold-backed derivative can be digitized. Physical gold can't. |
|
|
|
Not sure what you mean by "light". We have a pruning branch which drops most blockchain data but still functions as a full node, and a design for an SPV-like wallet.
Mobile wallets are planned but not under immediate development. Third parties may take that on once the libraries for SPV-like wallet functions are released, or if the project grows we might do it ourselves. Hard to say at this point.
Will there ever be an ELI5 version of how a cryptographic ring based blockchain can implement pruning? The whole concept fucks me up. If any input can at any time become an output at any point in the future when needed, how can you safely prune *any* of it? Of course I am still learning about how it all works under the hood, so perhaps it's my understanding that is to blame. There is a FAQ up in the thread that explains how it works, advantages, disadvantages, etc. Summary is that only the outputs and spent key image set are retained. The rest of the transaction (which is the vast majority of its size) is dropped |
|
|
|
i am sorry for not following the development of aeon,
Is it light? Do you have mobile wallet?
Just curious.
Not sure what you mean by "light". We have a pruning branch which drops most blockchain data but still functions as a full node, and a design for an SPV-like wallet. Mobile wallets are planned but not under immediate development. Third parties may take that on once the libraries for SPV-like wallet functions are released, or if the project grows we might do it ourselves. Hard to say at this point. |
|
|
|
|
We received a nice 1000 donation in addition to regular mining blocks and small donations of 5-10. All are appreciated!
balance: 457887.934933436883, unlocked balance: 456887.934933436883
|
|
|
|
As a Clam holder I would appreciate ending the digging process. Especially since it has been a while. People who are interested in Alt-coins probably have heard of clams by now. The end of digging could bring more interest and money into the coin.
Is it possible to prevent further digging though? Isn't digging just using a previously unused private key to move coins. So to prevent that we would have to remove the ability to send coins which were initially distributed but have yet to be moved?
Yes, and as a bitcoin holder I would like it if they stopped block rewards. We can stop staking for clams too. The whole point of clams is that they were fairly distributed, just because some have taken longer than others to dig theirs, it doesn't mean they shouldn't be able to. I agree that stopping the digs altogether is not the best solution. What about a halving of the Dig rewards in May 2016 (2 years from the launch date) as indicated in the previous page? We can expand this further that every subsequent halving would be twice the number of years as the previous one. The dig rewards would look like this: May 2014 - 4.6 May 2016 - 2.3 May 2020 - 1.15 May 2028 - 0.575 May 2044 - 0.2875 May 2076 - 0.14375 May 2140 - 0.071875 How about we take your coins and cut them in half next year instead. Save CLAM by leaving it the fuck alone. |
|
|
|
c. some kind of decay in value of undug CLAMs over time
This already exists. If you dig and stake, your CLAMs increase by about 4% per month currently. Assuming you have a sufficient number to actually stake, due to the lottery-style staking. You can stake in a pool. I've been offering to stake for people at no fee whatsoever (in order to try to decentralize the network from the current situation where JD has the vast majority of the stake), which will generate reasonably consistent daily income. |
|
|
|
c. some kind of decay in value of undug CLAMs over time
This already exists. If you dig and stake, your CLAMs increase by about 4% per month currently. In about a year they are increased by 50%. By not digging you lose 1/3 of that value in a year. That seems quite sufficient to me. This rate will decrease over time, but then the supply effect of even large digs will also decrease as the total supply increases. EDIT: previously stated that half of value was lost per year by not digging but correct number is 1/3 (150 if digging 100 and staking for a year vs 100 if waiting a year to dig). |
|
|
|
git checkout -b aeon
If you remove the -b there, you won't create a new branch and don't need to pull into it. Less confusing. So just git clone https://github.com/Arux-BTT/cryptonote-universal-pool.git your_pool_folder
cd your_pool_folder
git checkout aeon
However, if you want to make local changes the original method is fine, or even better create your own new branch with a different name forked from the aeon branch: git clone https://github.com/Arux-BTT/cryptonote-universal-pool.git your_pool_folder
cd your_pool_folder
git checkout aeon
git checkout -b my_new_branch |
|
|
|
|
Show Posts
