Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 725. (Read 4670673 times)
December 23, 2015, 02:14:34 AM
Monero is mentioned here https://bitcoinmagazine.com/articles/is-bitcoin-headed-for-a-break-in-fungibility-1450823559
December 22, 2015, 09:50:26 PM
...
That's right, you can safely delete blockchain.bin.
As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe
The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.
That's right, you can safely delete blockchain.bin.
As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe
The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.
Compressing the .bitmonero directory on Ubuntu GNU/Linux with 7z produces a compressed size of 4.5 GB. The uncompressed size is 14.1 GB. The Windows file system is likely applying some compression on the fly to get the file size down from 14 GB to 8 GB. I am using bitmonero v0.8.8.7-9292c1e.
December 22, 2015, 09:09:26 PM
Give up guys, this coin is dead!
Only 9 pull requests merged today
Only 9 pull requests merged today
December 22, 2015, 07:25:07 PM
If it is windows then dumbly for sure. lol. Thanks a lot guys.
December 22, 2015, 07:22:42 PM
Well according to multiple explorers I am all synced up and even a block ahead of some, hehe. So it seems that I do not need the deprecated blockchain.bin any longer with newer versions of the core correct? That will save some space for sure. I guess then you all have another node now up and running.
That's right, you can safely delete blockchain.bin.
As for the size of the LMDB database, some things are stored more than once, for speed, but some stuff is also wasted, so there is some scope to shrink it a bit. There's other stuff that needs changing in there, so I'm not saying it'll be smaller when all is said and done, but... maybe
The database also uses sparse files. Here, for instance, the logical size of data.mdb is 14 GB, but the actual data is 8 GB. There are "holes" in the file (0 filled preallocated data) that some filesystems use for other stuff, but some don't. I'm not sure whether Windows' filesystem does things cleverly or dumbly there.
December 22, 2015, 07:15:06 PM
Well according to multiple explorers I am all synced up and even a block ahead of some, hehe. So it seems that I do not need the deprecated blockchain.bin any longer with newer versions of the core correct? That will save some space for sure. I guess then you all have another node now up and running.
December 22, 2015, 07:11:02 PM
Any monero devs like to comment on this article? Come on, show us how this is totally wrong. Make sure to use facts. Uhh ohh....
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
That is an old article that contains no proof for those allegations. No further comment is necessary. Old news
December 22, 2015, 07:05:31 PM
Any monero devs like to comment on this article? Come on, show us how this is totally wrong. Make sure to use facts. Uhh ohh....
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
That is an old article that contains no proof for those allegations. No further comment is necessary. Old news
December 22, 2015, 07:04:02 PM
If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.
LMDB should make development and usability much better for all new features not limited to the GUI.
The amount of work done over the past year has been tremendous. The groundwork performed to date will make things much easier in the future.
December 22, 2015, 07:00:03 PM
Any monero devs like to comment on this article? Come on, show us how this is totally wrong. Make sure to use facts. Uhh ohh....
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
What NSA created Cryptonote for:
https://criticl.me/post/what-nsa-created-cryptonote-2292
December 22, 2015, 06:22:08 PM
So I have fully synchronized with the monero blockchain on 0.9 beta windows. These are inconsistencies I have noticed:
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
I'm not running the windows beta, but in response to #2, that sounds about right: the blockchain is ~14 Gb on my computer.
On a fully synced windows host I get:
File: C:\ProgramData\bitmonero\lmdb\data.mdb
Size: 10.0 GB (10,737,418,240 bytes)
December 22, 2015, 06:12:45 PM
So I have fully synchronized with the monero blockchain on 0.9 beta windows. These are inconsistencies I have noticed:
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
[1] Are you sure it isn't still syncing? Check the blockheight at the daemon and compare that with the blockheight on https://moneroblocks.eu. I think the green line in bitmonerod (stating something like, you are now fully synced and are able to use simplewallet) already appears somewhat before you are fully synced. LMDB only takes what it can take (during syncing). If much of your RAM is already allocated, LMDB won't take it while syncing. In other words, it won't get stuck like for instance the old binaries. After syncing it only takes <100 MB.
[2] That seems to be correct, the RAW file is around 2.3 GB. The size reported by you is the database representation used by the daemon. In my opinion, 14 GB isn't that much if you have a decent PC with a decent HDD/SSD. Currently, most of them have plenty of GBs and 14 GB is relatively small compared to that.
[3] If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.
Well blockchain.bin is the old one and isn't needed. The DB is ~10GB on Windows currently. Note that a lot of data is duplicated right now, and there is room for more clever optimizations in the future.
LMDB will indeed take memory if it's available, not just during syncing. My working set for example is ~4.5GB right now, but only ~52MB of that is private. The rest is ready to be given to other processes if they need it.
December 22, 2015, 05:48:11 PM
So I have fully synchronized with the monero blockchain on 0.9 beta windows. These are inconsistencies I have noticed:
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
[1] Are you sure it isn't still syncing? Check the blockheight at the daemon and compare that with the blockheight on https://moneroblocks.eu. I think the green line in bitmonerod (stating something like, you are now fully synced and are able to use simplewallet) already appears somewhat before you are fully synced. LMDB only takes what it can take (during syncing). If much of your RAM is already allocated, LMDB won't take it while syncing. In other words, it won't get stuck like for instance the old binaries. After syncing it only takes <100 MB.
[2] That seems to be correct, the RAW file is around 2.3 GB. The size reported by you is the database representation used by the daemon. In my opinion, 14 GB isn't that much if you have a decent PC with a decent HDD/SSD. Currently, most of them have plenty of GBs and 14 GB is relatively small compared to that.
[3] If you mean the third party GUIs, that is correct. I think the developers of them will merge LMDB when it is officially released.
December 22, 2015, 05:41:34 PM
So I have fully synchronized with the monero blockchain on 0.9 beta windows. These are inconsistencies I have noticed:
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
I'm not running the windows beta, but in response to #2, that sounds about right: the blockchain is ~14 Gb on my computer.
December 22, 2015, 05:37:26 PM
Monero Specifications
•PoW algorithm: CryptoNight [1]
•Max supply: Infinite (see note below) [2]
•Block reward: Smoothly varying [3]
Finally fixed the max supply. Nice stealth update! So now the coin has infinite amounts! LOL
TO INFINITY AND BEYOND LOL!
•PoW algorithm: CryptoNight [1]
•Max supply: Infinite (see note below) [2]
•Block reward: Smoothly varying [3]
Finally fixed the max supply. Nice stealth update! So now the coin has infinite amounts! LOL
TO INFINITY AND BEYOND LOL!
December 22, 2015, 05:31:57 PM
So I have fully synchronized with the monero blockchain on 0.9 beta windows. These are inconsistencies I have noticed:
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
1) The private working set of memory is now manageable and small, unfortunately the whole working set is the same as in previous versions of bitmonerod. Around 8Gb and machine is struggling.
2) I now have a blockchain.bin of around 4.8Gb but also a Db file of another 10Gb which is unacceptable in storage terms.
3) The beta does not work with any of the gui versions but that is to be expected and I assume rectified shortly in development.
The speed of the sync was actually quite faster that I expected and there is good connectivity of nodes which is good as well.
Has anyone else running the beta code noticed issues similarly?
December 22, 2015, 05:31:06 PM
Is anyone taking this trolling seriously?
Neigh.
Where is your defender of the realm, icegayblaster? Is he hiding because he knows he will have his ass handed to him by yours truly? #MONEROISGAYNeigh.
Hey guys, here is my plan. I plan to make you look like the liars you are and hopefully soon your coin will be completely dead. Do you think I can cost you at least half of your coin's value be the end of January? I mean, that's only 5 million. Have a nice day.
December 22, 2015, 05:16:41 PM
Is anyone taking this trolling seriously?
Neigh.
Where is your defender of the realm, icegayblaster? Is he hiding because he knows he will have his ass handed to him by yours truly? #MONEROISGAY Neigh.
December 22, 2015, 05:13:27 PM
Today is December 21, 2015. Could we compare our way, passed and to be passed, with roadmap declared by core devs on January 5th, 2015?
I call moderators don't feed trolls and to remove spam from the thread. I apologize if my original post has triggered their stupid attack.
Returning to the my initial question, can devs say, what is simply done from the wishes they had positioned on January 5th, 2015? And what is the future roadmap?
You didn't do anything except point out what a useless bunch of commie devs you have. Did they eat too many Cheetos instead of having a good security model with no back doors and a gui? The world will never know.
December 22, 2015, 05:04:32 PM
There it is folks, if you want to know if this coin is secure, go ahead and pony up the money.
https://i.imgur.com/RsUwz6c.png
https://i.imgur.com/XTZylY9.png
https://i.imgur.com/48bXVZd.png
Quit horsin' around.
How about you audit your code you bald faced liar. And what about the gui?
Jump to: