DEV LEFT THE PROJECT
Totally. I left to sulk and will only come back when I decide to.
Which will likely be as soon as I have another patch ready.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 729. (Read 4671575 times)
December 21, 2015, 08:46:14 AM
Totally. I left to sulk and will only come back when I decide to.
Which will likely be as soon as I have another patch ready.
December 21, 2015, 07:53:56 AM
First part no (AFAIK), second part yes (slowly tends towards infinity if you wait long enough, at least theoretically).
December 21, 2015, 07:34:16 AM
December 21, 2015, 06:23:38 AM
I think this coin is going to get dumped hard soon because 40 btc buy support is very weak.
December 21, 2015, 05:14:55 AM
Happy Xmas dear core devs and all the members of Monero community!
Let us to summarize what is done in departuring 2015 from the following wishes:
from here:
https://forum.getmonero.org/1/news-announcements-and-editorials/134/monday-monero-missives-22-year-in-review-january-5th-2015
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?
Let us to summarize what is done in departuring 2015 from the following wishes:
Quote
Monero Monday Missives
January 5th, 2015
-- SKIPPED --
Looking Forward: 2015
We have a lot in the pipeline for 2015. A few things that we'd like to highlight that you can look forward to:
more MRL academic goodness, including some of the work started at our MRL mini-meetup from 2014
a finalised, working, tested blockchain DB implementation using LMDB
i2p integration
some additional blockchain DB implementations
finalisation and release of the Monero core GUI
the release of smart mining functionality
the finalisation of a complete overhaul of the RPC functionality
HTTPS and simple auth support for RPC servers
a new, unified, well-documented RPC interface
blocknotify and walletnotify equivalents in the daemon and wallet client
a complete replacement of the wallet/server IPC with 0MQ
multi-signature transactions
open-sourcing the Monero Forum software
the release of some OpenAlias sub-projects
And, undoubtedly, much more both for Monero core and related external projects.
January 5th, 2015
-- SKIPPED --
Looking Forward: 2015
We have a lot in the pipeline for 2015. A few things that we'd like to highlight that you can look forward to:
more MRL academic goodness, including some of the work started at our MRL mini-meetup from 2014
a finalised, working, tested blockchain DB implementation using LMDB
i2p integration
some additional blockchain DB implementations
finalisation and release of the Monero core GUI
the release of smart mining functionality
the finalisation of a complete overhaul of the RPC functionality
HTTPS and simple auth support for RPC servers
a new, unified, well-documented RPC interface
blocknotify and walletnotify equivalents in the daemon and wallet client
a complete replacement of the wallet/server IPC with 0MQ
multi-signature transactions
open-sourcing the Monero Forum software
the release of some OpenAlias sub-projects
And, undoubtedly, much more both for Monero core and related external projects.
from here:
https://forum.getmonero.org/1/news-announcements-and-editorials/134/monday-monero-missives-22-year-in-review-january-5th-2015
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?
December 21, 2015, 04:44:14 AM
Fluffypony interview on Bitcoin Uncensored, starting at 59:54:
https://soundcloud.com/bitcoinuncensored/e20-christmas-poo-122215
https://soundcloud.com/bitcoinuncensored/e20-christmas-poo-122215
December 20, 2015, 11:02:02 PM
Ok, wondering if someone can help.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
It seems you're trying to programmatically drive simplewallet ?
If so, your description looks very much like simplewallet's working directory is not the one you think it is, and your wallet saved while automated is elsewhere on your computer.
If you're on Linux, /proc/`pidof simplewallet`/cwd is a symlink to the program's current working directory.
Ah, yes, you are right. It's being saved to my debug folder for some reason.
Not the Monero .keys file though
I think it's different for different situations. But I found it by searching the entire computer for the name of the .keys file.
December 20, 2015, 08:01:39 PM
Our Devs are legendary. I have total faith in their abilities and the sheer intellect of our core team, and even many of our long time members give me the assurance that Monero is -the- digital cash of the future. 
Legendary Devs confirmed.
RING CONFIDENTIAL TRANSACTIONS
https://eprint.iacr.org/2015/1098.pdf
https://www.reddit.com/r/Bitcoin/comments/3xkuuq/ring_signature_confidential_transactions_for/
December 20, 2015, 01:09:14 PM
Ok, wondering if someone can help.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
It seems you're trying to programmatically drive simplewallet ?
If so, your description looks very much like simplewallet's working directory is not the one you think it is, and your wallet saved while automated is elsewhere on your computer.
If you're on Linux, /proc/`pidof simplewallet`/cwd is a symlink to the program's current working directory.
Ah, yes, you are right. It's being saved to my debug folder for some reason.
Not the Monero .keys file though
December 19, 2015, 11:15:11 AM
Ok, wondering if someone can help.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
It seems you're trying to programmatically drive simplewallet ?
If so, your description looks very much like simplewallet's working directory is not the one you think it is, and your wallet saved while automated is elsewhere on your computer.
If you're on Linux, /proc/`pidof simplewallet`/cwd is a symlink to the program's current working directory.
Ah, yes, you are right. It's being saved to my debug folder for some reason.
December 19, 2015, 07:48:33 AM
Ok, wondering if someone can help.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
It seems you're trying to programmatically drive simplewallet ?
If so, your description looks very much like simplewallet's working directory is not the one you think it is, and your wallet saved while automated is elsewhere on your computer.
If you're on Linux, /proc/`pidof simplewallet`/cwd is a symlink to the program's current working directory.
December 19, 2015, 07:35:26 AM
I think Monero is in the final stage of accumulation. I see every day the bulls are trying to increase the price. Optimistic predictions
December 19, 2015, 07:23:35 AM
Ok, wondering if someone can help.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
I'm opening simplewallet and creating a new wallet and doing so by using a sendkey(i.e. sendkeyboard) to the process via another program, but when the wallet is created, the .keys file does not show up in the folder.
If I try to run it again, using the same process, I don't generate another wallet but open an existing one, but I still can't see it.
Now, if I manually open simplewallet and enter a wallet with the same name as before, I can create a new wallet and I CAN see the files.
But if I delete this wallet file (which includes .keys, etc) but I again run the program and use sendkey method on simplewallet, I cannot generate a new wallet. I still get the same invisible wallet as before.
I cannot figure out why I can open an invisible .key file. I can generate a new file of same name manually opening simplewallet and using command line but when I run my program, it's somehow "seeing" that invisible file.
December 19, 2015, 04:47:30 AM
Another day and another 3 PRs merged. Thank you cow and pony
Another day waiting for the definition of "soon"
Another day waiting for the definition of "soon"
Our Devs are legendary. I have total faith in their abilities and the sheer intellect of our core team, and even many of our long time members give me the assurance that Monero is -the- digital cash of the future.
December 18, 2015, 08:37:27 PM
Another day and another 3 PRs merged. Thank you cow and pony
Another day waiting for the definition of "soon"
Another day waiting for the definition of "soon"
December 18, 2015, 04:01:17 PM
2. One small tweak to make running over Tor work better (DNS requests go through Tor rather than being blocked or leaking).
We thought #2 especially would be appreciated in the 0.9 release.
That is a pretty neat feature! Or rather a bug fixed. Are there any other caveats running monero privately?
Not that I'm aware of other than the usual pitfalls of not always doing everything correctly. Script as much as possible and make sure your scripts are robust and correct before you expect to be operating privately. Recheck everything after updates or changes.
Ultimately running on a proxy VM like whonix is probably safer, but using Tor directly is a viable option now.
December 18, 2015, 03:07:46 PM
2. One small tweak to make running over Tor work better (DNS requests go through Tor rather than being blocked or leaking).
We thought #2 especially would be appreciated in the 0.9 release.
That is a pretty neat feature! Or rather a bug fixed. Are there any other caveats running monero privately?
Getmonero page should add a user guide with detailed instructions and explanation how to use monero anonymously. While waiting for i2p to simplify things, people interested in using monero with such high privacy demands could start and bootstrap the kind of economy, where privacy is crucial.
December 17, 2015, 05:57:21 PM
2 pull requests from warptangent were just merged.
Daddy are we there yet?
Daddy are we there yet?
Not sure. I thought I heard something about a 'code freeze' prior to release?
Its more like thick slush. For the most part the code is frozen now, outside of a last few issues, mostly build-related.
Anyway, the commits from warptangent were:
1. A few for pure cleanup (fixing a typo in a message and replacing tabs with space in the source code).
2. One small tweak to make running over Tor work better (DNS requests go through Tor rather than being blocked or leaking).
We thought #2 especially would be appreciated in the 0.9 release.
December 17, 2015, 09:17:46 AM
2 pull requests from warptangent were just merged.
Daddy are we there yet?
Daddy are we there yet?
Not sure. I thought I heard something about a 'code freeze' prior to release?
Jump to: