i don't expect squat (re price) with then new release unless their are those that "invest" based on "performance" of a core team.

i mean, really, besides the ability of the network to perform its primary function, there is the ability of the network to perform that function in a secure fashion. 0.9 will allow many more nodes to come online... we've all witnessed newcomers to the scene be like "yo i downloaded this thing on the website and wtf". So 0,9 will make that whole situation somewhat better.

but as was eluded to in that fast talkin bitcoin podcast, its all about network security. And our hashrate just doesn't cut it yet. What cuts it? I have no idea. As a supporter, you can do many things:

1. run a solo node and mine on it
2. build up massive mining infrastructure
3. keep the price high

the current evolution of crypto allows #3 to work in some extent to address the overarching problem - lack of net hash. If monero was worth 10$ at current emission, what would the net hash be? so many cloud services would be burned keeping it up. But thats not what we want. We want a natural net hash. We want organic. Home grown. A real network of contributors. A real network of miners with dedicated rigs.

Yes it has been posited that we're just not there yet to justify high net hash..... but when? when the emission curve is bollux?

i don't expect squat (re price) with then new release unless their are those that "invest" based on "performance" of a core team.

i mean, really, besides the ability of the network to perform its primary function, there is the ability of the network to perform that function in a secure fashion. 0.9 will allow many more nodes to come online... we've all witnessed newcomers to the scene be like "yo i downloaded this thing on the website and wtf". So 0,9 will make that whole situation somewhat better.

but as was eluded to in that fast talkin bitcoin podcast, its all about network security. And our hashrate just doesn't cut it yet. What cuts it? I have no idea. As a supporter, you can do many things:

1. run a solo node and mine on it
2. build up massive mining infrastructure
3. keep the price high

the current evolution of crypto allows #3 to work in some extent to address the overarching problem - lack of net hash. If monero was worth 10$ at current emission, what would the net hash be? so many cloud services would be burned keeping it up. But thats not what we want. We want a natural net hash. We want organic. Home grown. A real network of contributors. A real network of miners with dedicated rigs.

Yes it has been posited that we're just not there yet to justify high net hash..... but when? when the emission curve is bollux?

Newton was a fad.  Palm was a productivity tool.  Usability features are converging, and the demand will come, inevitably.  As long as the usability is there when the demand spike emerges (at some sweet, stochastic moment) the outcome should be quite nice.  Maybe it needs a GSM radio to reach a subsequent tier of market expansion, but first things first, walk then run.

Bd7: 3 votes (boolberry, XMRpromotions, ING Bank)
Kg7: 1 vote (LucyLovesCrypto)

Live on iTunes though -> https://itunes.apple.com/us/podcast/the-monero-missive-podcast/id1032156854?mt=2


In case you don't have iTunes -> http://podbay.fm/show/1032156854/e/1451151298?autostart=1

EDIT: FYI: There is some discussion in the missive about I2P vs TOR. However, if I understood correctly, you can run I2P either as I2P-only, I2P/IP bridged or IP-only (see -> https://getmonero.org/design-goals/). Thus, the latter will still make it possible for you to run Monero over TOR socks. I am not entirely sure about this, so if what was stated is incorrect, feel free to correct me.

gxh4 2 votes (boolberry, tifozi)

kudos to those who were opposing draw earlier. I think a non draw outcome is a real possibility now.

3. Blockchain bloat solution (already implemented):
http://boolberry.org/files/Boolberry_Reduces_Blockchain_Bloat.pdf

Pruning FAQ

Q: What is pruning?

A: Pruning refers to removing unnecessary information from the blockchain once it is no longer needed.

Q: What are the advantages?

A: Pruning reduces the amount of storage needed for the blockchain. If the blockchain is loaded into RAM (which is the case in the current implementation), then it also reduces RAM usage. Finally, it also reduces the rate that these resources are consumed over time as the blockchain grows. In the current implementation, each time one new block is accepted, one old block is pruned, on average freeing up a large portion of the resources needed for the new block.

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. There is a current limitation that after extended period of disconnection (>28 days) a node may have trouble resynchronizing with the network, and would need to be reset. This is not inherent and should be addressed later.

Q: Does pruning reduce the effectiveness of ring signatures for transaction privacy?

A: No, ring signatures and privacy are unaffected.

Q: How is pruning enabled and disabled?

A: Using the --pruning option on the daemon command line. With this option the daemon will prune the blockchain and will also switch from using the blockchain.bin file for storage to blockchain-pruned.bin. To switch an existing node into pruned mode, copy blockchain.bin to blockchain-pruned.bin before starting the daemon with --pruning. To switch pruning off, remove the --pruning option. Do not, however, copy blockchain-pruned.bin to blockchain.bin. This will not work. You will need to have an unpruned blockchain.bin file or resync unpruned from the network.

Q: How does AEON's pruning compare with Boolberry's pruning?

A: AEON prunes slightly more information from the blockchain, so the required storage is slightly smaller (given equivalent usage), though the difference is likely not particularly significant. BBR prunes the blockchain on the entire network while AEON prunes on each node individually (and only if pruning is enabled). This means that new nodes can come online faster with BBR, but those new nodes are unable to independently verify the entire blockchain. It is possible to download an unpruned BBR blockchain from a web site to independently verify it, but in that case the amount of data downloaded would be the same as AEON. It also means that every BBR node is able to serve the chain to new users but in AEON this function falls to nodes that are unpruned, also known as "archive nodes" (or alternately via a trusted bootstrap file).

Q: How does AEON's pruning compare with Bitcoin's pruning?

A: In Bitcoin 0.11, the same model of pruning is implemented as in AEON. That is, nodes prune blocks locally, after syncing from an unpruned chain and verifying the chain independently. Like AEON, Bitcoin pruned nodes can't rescan or reindex wallets. Bitcoin 0.11 does not support wallets on pruned nodes at all, so it currently has more limitations that AEON. Old Bitcoin blocks must be retrieved from unpruned archive nodes, as with AEON.

Q: What other coins implement pruning?

A: Other than Boolberry, Bitcoin, and possibly some coins which have inherited their implementation by being Bitcoin forks, no other coins implement pruning at this time.

Q: What's this about "archive nodes"? How can I run one?

A: When nodes connect to the network, they retrieve blocks from other nodes. If only blocks within the most recent 10 000 (approx.  28 days) are needed for syncing, even pruned nodes can provide them. However, in the case of nodes which are brand new (syncing from the genesis block) or which have been offline for >28 days, pruned nodes will be unable to supply the older blocks. Instead this task falls to unpruned nodes, also known as archive nodes. For the time being the project-run seed nodes will always run in unpruned mode, and others with sufficient RAM and storage space who wish to support the network are also encouraged to do so. To run an archive node, simply start the daemon in the normal manner, without the --pruning option.

Q: What are the numbers? How much does pruning reduce the amount of memory and storage needed?

A: The exact numbers will vary according to OS, compiler, etc. and also depend on the usage of the blockchain in the future. One early report from BoscoMurray stated, "RAM usage down from 4.8GB to 2.4GB and blockchain file size down from 3.2GB to 1.7GB"

Q: That doesn't seem like a big reduction. Why is the benefit not greater?

A: To explain why the reduction is not larger and understand what this means for the future, let's first review some basics of how a blockchain works.

Every time a coin is spent, a digital signature accompanies the transaction in order to show that the owner of that coin authorized spending it. Once this signature is checked, it is no longer needed. This is the largest portion of what is being pruned. In the cryptonote signature scheme (used by AEON), ring signatures used for anonymity, which means while a signature shows the coin owner authorized the transaction, unlike conventional signatures, it does not identify the specific coins being spent, and therefore does not allow tracing and analyzing the blockchain. As a side effect of this functionality, these signatures are much larger than ordinary digital signatures (a fact sometimes described as "cryptonote bloat"). Thus in AEON, pruning offers great benefit and eliminates the "cryptonote bloat".

So why is the savings not larger? Because in the early history of AEON, there was a very large number of very large transactions and many of those transactions did not using ring signatures. This happened for several reasons, including a major flaw in the early versions of cryptonote mining pool software. Thus, while the chain is relatively large, a relatively small amount of storage is saved by pruning the early transactions.

The newer transactions are a different story. The pool software flaw was fixed long ago, and most transactions now do use ring signatures. So the savings from pruning going forward should be much higher (perhaps 75-80%). Of course, since ring signatures are now being routinely used, it means that that actual anonymity of the coin in practice is greatly improved, and with pruning there is no long term storage cost (i.e. no "cryptonote bloat") for most nodes (other than archive nodes). We get the best of both worlds!

Q: What about a database or disk-based block storage? Doesn't that also reduce memory usage?

A: Storing the blockchain out-of-memory in a database or in cache files reduces memory usage but does not reduce storage usage nor reduce the rate of growth of storage usage over time. In AEON, the plan is to later support out-of-memory storage of the blockchain along with pruning, so memory usage will be further reduced, and storage usage will remain low and grow very slowly over time.

This is likely to be the case. CryptoNote was designed to be different from Bitcoin; even its whitepaper is written as opposed to Bitcoin architecture. Therefore, the API is incompatible. This would not be a drawback in case of higher demand/hype, but in reality this may hinder CryptoNote much more than blockchain bloating.

This project allows developers to flawalessly access the functionailty of Monero applications through the Core assemblies' RPC services. As the software is open-source, everyone can contribute, achieving the best performance and reliability for end-users.

Why is this API necessary?
It makes the implementation of Monero extremely easy for merchants, wallet builders, and all the other developers who are interested in working with (or accepting) Monero. Also, the core developers can concentrate more on the internals (instead of spending time on the official GUI client), which means that the currency should advance faster.

Is it cross-platform?
The first 3 releases of the API were only made for desktop PCs running Microsoft .NET Framework 4.5 or higher, thus, resulting in a smaller userbase than wanted. Since v3, the project has been split into 2 subprojects, one which is responsible for communicating with the daemon and the account manager's RPC channel, and one which can manage the required processes on PC.

What kind of platforms can utilize the power of Monero API .NET, then?
Basically every device which has support for running the Microsoft .NET Portable Framework v4, and more: Microsoft is planning to provide native (C++) compilation of C# assemblies very soon, and this process can be even faster since .NET Core has been made open-source.
The project can run on PCs (Windows; Mac and Linux with Mono .NET), mobile phones (Windows Phone; Android and iOS with Xamarin), and even on video game consoles like Xbox.

How does it work?
As I have already mentioned above, the project consists of 2 parts: MoneroAPI, and MoneroAPI.Extensions. The first one is built as a PCL (portable class library) and is multiplatform, while the extensions are desktop-only and contain functions for hosting a full node. Basically, MoneroAPI is preferable for lightweight, client-only applications, and MoneroAPI.Extensions adds support for hosting the Monero Core processes with ease.
There is a demo project included in the GitHub repository for a more technical explanation.

---

3. Blockchain bloat solution (already implemented):
http://boolberry.org/files/Boolberry_Reduces_Blockchain_Bloat.pdf

Another one:


Link: http://eprint.iacr.org/2015/1098

I still think Kg7 is only option. Maybe not h5 right away after g4, but first Re8. The white position has a weak spot with g4. We better exchange queens if our queen is only defending a pawn, and the white queen has many attacking threats. Also Re8 right away is better than Rc8. That Qf8 variant I overlooked, but saying I have no clue makes no sense.

Just trying to make suggestions, so together we find the best move. That's why I asked if I only give my move, or also give suggestions. I hope you all look at all the possibilities Kg7 gives, that was my only intention. Kg7 to me looks like our only chance.

I still think Kg7 is only option. Maybe not h5 right away after g4, but first Re8.

Qg6: 6 votes (ING Bank, galdur, LucyLovesCrypto, languagehasmeaning, jjacob, XMRpromotions)
Re8: 1 vote (Rolf Uhlhorn)

Rfc8

34.Qd4 Bxa4 he´ll get the b and d pawns resulting in even material but it takes two tempos which should give us time for some counterplay. The position is becoming rather simplified at that point.

Thank you, but we won't play Rxd2, but Be6 for example. But I am just trying to make suggestions, I decide during daytime.

Thank you, but that is what I thought I said: "Bg2+ has some funny effects, but won't work out." 30. ... - Bg2+ is funny, but not ok.

After 30. .. - Re8 31. Qxf6 - Re2, not Bg2+. If Qd8+ - Kg7 / Qxd3 we win his queen with Rxh2+ etc. But I look at it during daytime, after 4 am here, my eyes are closed and my brain not working properly.

Well, we´re a pawn up as it is so losing one may not be so horrible.

Here´s a line: 30. Qxe5 Qg6 31. Rc6 Rc8 32. Rxc8+ Bxc8 33. Bc4 Bd7 34. b3 g4 35. f4 Bf5 and if 36. Bxa6 Ne4 with excellent prospects for black.