THIS IS GENTLEMEN!
moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.
Looks great!
Anyone have an idea why there is such a large percentage of 7.8255 XMR sized transactions?
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 737. (Read 4671575 times)
December 03, 2015, 01:10:35 AM
THIS IS GENTLEMEN!
moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.
Looks great!
Anyone have an idea why there is such a large percentage of 7.8255 XMR sized transactions?
December 02, 2015, 09:30:14 PM
Anyone tried building for ARM and running on a tablet or raspberry pi? Do you also need to use BDB there?
Yes and yes
Quote
Also, is there (plans to implement) an RPC or 0MQ call to shutdown bitmonerod or simplewallet (gracefully)?
Pull requests accepted.
December 02, 2015, 09:27:15 PM
Anyone have working win32 binaries that they compiled? Is it really tricky to build Berkeley DB on windows?
Anyone tried building for ARM and running on a tablet or raspberry pi? Do you also need to use BDB there?
Can you build a simplewallet target without any database, LMDB or BDB, for win32 or ARM?
Also, is there (plans to implement) an RPC or 0MQ call to shutdown bitmonerod or simplewallet (gracefully)?
Anyone tried building for ARM and running on a tablet or raspberry pi? Do you also need to use BDB there?
Can you build a simplewallet target without any database, LMDB or BDB, for win32 or ARM?
Also, is there (plans to implement) an RPC or 0MQ call to shutdown bitmonerod or simplewallet (gracefully)?
December 02, 2015, 05:17:40 PM
Git updates since last time:
Since last post:
- the IP banning code from Aeon got merged, and new commands/RPC for managing bans
- wallet refresh speedup (both parallelizing things, and avoiding others)
- a --restricted-rpc for the daemon (so others can't mine on your public node, for example)
- an option to let the wallet autmatically refresh periodically from the daemon
- a new show_transfers command to display transactions in a more useful way
- outgoing transactions info is now kept in the wallet cache so show_transfers can be even more useful
- the daemon will relay transactions periodically if they stay in the pool for too long (if they failed to relay, for instance if the network connection was down when the tx was first sent, for instance)
December 02, 2015, 01:10:04 PM
THIS IS GENTLEMEN!
moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.
marvelous work!
now its blatantly obvious how opaque monero transactions really are. There'll be a tip coming your way!!!
December 02, 2015, 11:54:04 AM
THIS IS GENTLEMEN!
moneroblocks.eu now shows the participating outputs in each ring signature. Enjoy.
December 02, 2015, 10:05:59 AM
Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".
I think I know what the problem is. It requires a coder with Windows (and some knowledge of windows APIs) to add a bit of code though. In contrib/epee/include/console_handler.h, the wait_stdin_data needs some code to implement what the select does (wait till there is data on stdin, while we're not told to stop). As it is, the Windows version will not care about that and go into a blocking std::getline, and I think there's a good chance you're getting stuck in that. Anyone with the above description to do this ? It's pretty simple if you know the right Windows API for this (assuming the API is not stupidly).
On the other hand, I run a daemon on Windows and *never* have to exit twice. Though, if I "exit" while the daemon is still starting up, craziness happens (it has to be killed).
December 02, 2015, 05:59:20 AM
Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".
I think I know what the problem is. It requires a coder with Windows (and some knowledge of windows APIs) to add a bit of code though. In contrib/epee/include/console_handler.h, the wait_stdin_data needs some code to implement what the select does (wait till there is data on stdin, while we're not told to stop). As it is, the Windows version will not care about that and go into a blocking std::getline, and I think there's a good chance you're getting stuck in that. Anyone with the above description to do this ? It's pretty simple if you know the right Windows API for this (assuming the API is not stupidly).
December 02, 2015, 05:04:16 AM
Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?
It was reported previously on some systems. Enter 'exit' again.i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?
Code:
2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
The CPU load returns to "normal" but the process does not store and exit....2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Same issue with beta version for Windows (2015-Nov-01). Sometimes daemon successfully closes after first "exit" command, sometimes it needs to read second "exit".
December 02, 2015, 02:00:04 AM
Quote
My fullnode is running on the compiled version, for my "productive" environment i will wait for the official binaries 
Everyone is waiting official wallet
December 01, 2015, 09:31:11 PM
December 01, 2015, 04:29:38 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx
beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.
Yeeaaahhh, but i use Linux so the winbeta is like nuts for me
Needless to say, we all are waitng for the official release
Thanks for your help!
then its even easier! Just compile!
My fullnode is running on the compiled version, for my "productive" environment i will wait for the official binaries
December 01, 2015, 04:27:26 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx
beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.
Yeeaaahhh, but i use Linux so the winbeta is like nuts for me
Needless to say, we all are waitng for the official release
Thanks for your help!
then its even easier! Just compile!
December 01, 2015, 03:43:43 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx
beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.
Yeeaaahhh, but i use Linux so the winbeta is like nuts for me
Needless to say, we all are waitng for the official release
Thanks for your help!
December 01, 2015, 03:37:02 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx
beta release is in my sig. the official official is still getting its finishing touches. last i heard fluffy was working on the 32 bit compile.
December 01, 2015, 03:25:59 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
I assume you know what's comming now, when do we have the opportunity to officially get working with 0.9xxx
December 01, 2015, 03:13:13 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Yeah that's 8.6. Known issue, been pretty much fixed with new version
December 01, 2015, 02:17:24 PM
what about ctrl+c?
Code:
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
December 01, 2015, 02:15:35 PM
what about ctrl+c?
December 01, 2015, 02:13:10 PM
Hy Ladies and Gents,
i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?
It was reported previously on some systems. Enter 'exit' again.i got a small problem on Kubuntu 14.04 64bit
I want to exit bitmonerod v.08.8.6-release with the exit command, well nothing happens.
See the output form the terminal -> could you please advise what i can do?
Code:
2015-Dec-01 19:34:19.190466 [P2P8][192.241.219.6:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
The CPU load returns to "normal" but the process does not store and exit....2015-Dec-01 19:34:20.050032 [P2P2][80.71.13.55:18080 OUT] SYNCHRONIZED OK
2015-Dec-01 19:34:56.476377 [P2P8][184.166.185.230:18080 OUT] SYNCHRONIZED OK
save
2015-Dec-01 19:38:51.230558 Storing blockchain...
2015-Dec-01 19:41:34.489371 Blockchain stored OK.
exit
2015-Dec-01 19:41:39.634967 [node] Stop signal sent
^C2015-Dec-01 19:43:13.872076 [SRV_MAIN][node] Stop signal sent
exit
^C2015-Dec-01 19:46:29.085640 [SRV_MAIN][node] Stop signal sent
Jump to: