Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1149. (Read 4670673 times)

xmrmonero.com is a MEW project and is not a core team project (that is not to say that we don't support it or contribute to it or whatever).

The only sanctioned, official forum is forum.monero.cc

Can anyone here spit out some ideas concerning websites that you think should be created around or focusing on Monero?

I wrote yesterday a long reply regarding the GUI wallet on Reddit:
http://www.reddit.com/r/Monero/comments/2uqsl6/why_is_the_official_gui_wallet_not_released_yet/

I'll add support for that as soon as I can retrieve it from the core RPC.

Until then, here is an update I've just posted on the #monero-dev IRC channel:

Thanks for all the feedback provided! Right now, I'm working on fully separating the API part from the GUI, thus, I've created a new GitHub repository for Monero API .NET, which could be used by merchant services to easily utilize Monero core functions from the Microsoft .NET programming languages.

I've just gone on a 1-week holiday, though, but will try to continue the developments as soon as I have time (for instance, airplanes are perfect places for this task ).

If your concern is "hey I haven't seen a missive in a while" its because, in general, the dev team has moved to publishing missives after milestones are achieved.

In essence, the gist is "let the dev team dev", because I think the milestones are getting relatively more difficult to achieve compared to the first months of existence, where im assuming things were relatively easier, but Im just making this stuff up.

I'm trying to compile a weekly report by keeping an eye on the IRC channel and collecting useful thread posts.

So, since last monday, when I got this idea, here are some notable developments and posts that I've collected:
--------

"we're remerging/updating daemonize, working on RPC -> IPC (via 0MQ), beginning the refactor/extrapolation to libraries, and working on non-64-bit comparability. This is all directly related to the GUI effort"

There are apparently two mul128 implementations (whatever that is); fluffy was looking for insight into which one should be kept

There was general chatter on the non-dev monero channel about creating a faucet.

And my LMDB version of bitmonerod is still running fine (3 weeks now?)
-----------

with the blessing of the dev team (and/or the community, whatever), I could deidentify stuff and try to make a nice little published package. Be the "reporter" of XMR based on what I come across. Won't be as pretty as fluffy's.

Can we setup wikimedia on monero.cc or xmrmonero.com (i see a wiki page there but it doesnt show me anything)  so we can start adding info? Then, when time comes, you guys can do whatever changes you want but some articles will be ready...

DavidLatapie, you're producing some excellent literature. Thank you.

What exactly is the relation between https://xmrmonero.com/ and https://forum.monero.cc/? Which one is worth joining?

If you follow Monero carefully, you may have heard the word OpenAlias, without really understanding what it is.

OpenAlias (openalias.org) is an open standard for simpler addresses for any crypto — "Simplifying the World" is its slogan.

As long as you have a domain name (I recommend Gandi), you can transform these unreadable 35 characters long addresses (or even 96 for Monero) into something much more human-readable, like donate.monero.cc. Zooko's triangle: squared.

"At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralised and decentralised domain systems."

No risk of disappointments like "chris678". No risk of phishing like "poloniex". No risk of losing your alias because you lost your private key. To own the alias, you just own the domain name and that's all.

Raw address:

OpenAlias address:

Any domain. Any crypto. Any address. Any time.

Any domain. You can use any domain name, ICANN-sanctionned or not, as long as it follows the DNS naming system. This means OpenAlias works with .bit (Namecoin) too (but not with .onion and .i2p)

Any crypto. Even if OpenAlias is a Monero Core Team creation, it works with other cryptocurrencies as well. In fact, it works with any crypto. So, yes, you can receive bitcoins, ripples, NXT... with OpenAlias.

Any address. You can use the same address for several cryptos. The alias for the Monero development fund is donate.monero.cc and it has both a Monero and a Bitcoin address. So you don't have to remember one address per crypto. Just one address. Note though that an entry must be created for every crypto, so don't send us dogecoins that way, it won't work :)Also, the reverse is true: you can have several aliases with the same address. For instance, you can send to "david.latapie.name" or "latapie.name", I configured both (here too, this is manual, so if you send to "www.latapie.name", it won't succeed - www is deprecated anyway).

Any time. You can change the address whenever you want, it won't break the alias.

OpenAlias is fully implemented in the latest version of simplewallet (0.8.8.6) and on mymonero.com. We are in discussion with Poloniex to have implemented (for outgoing transactions only). For the moment, Monero is the only cryptocurrency to implement OpenAlias.

OpenAlias follows exactly the Three Pillars of Monero. Privacy: DNSSEC and DNSCrypt compliant and we provide log-less resolvers (list on the website). Decentralisation: ready for Namecoin, DIANNA, P2P-DNS and other decentralised DNS. Scalability: Zooko's triangle and future-proof.

We hope to see many implementations of OpenAlias soon!

This is a recurring question, from long-time holders and newcomers alike.

There is a misunderstanding here and we have to confess we have not been performing very well at dispelling it.

Truth is we are not trying to merely create a GUI, as in a GUI wrapper. Fact is these simple wrappers already exist (Jojatekok's Windows GUI, Neozaru's Qt GUI, jwinterm's lightWallet and we could probably use Bitcoin wallet too).

What we are building is more than a wrapper, it is a full-fledged scalable GUI software. And scalable is the hard part, not GUI - remember, scalability is one of the three pillars of Monero.

What is scalable?

• Mnemonic seed for increased security (why).
• Low RAM footprint ("the DB", presently Symas Lightning MDB but later a lot others, since we built a database API).
• e-commerce prerequisites, notably for payment processors.
• Low bandwith footprint (a framework for SPV, like Electrum). The remote node provides a similar experience in that one doesn't have to download the whole blockchain, but this is where the similarities end and SPV would be lighter than a remote node.

• Much better understood (thus secure) and refactored code. This is behind-the-scene stuff and not sexy, but when it comes to securing your money, this matters. The Monero Protocol is sound, but we are not that comfortable with the source code we inherited in April (and improved since then). Note: we are pretty demanding on security, so when we say that "we are not that comfortable", this means the security is already high, just not high enough
• Gitian binaries
• Various mainstream users niceties, such as an address book, an easy way to do bookeeping (including easily report to tax offices, because Monero is not meant just for l33t haX0r, but for everyone, including legal persons like corporations, NGO, political parties...)
• Viewkey for optional transparency (see fluffy quote on Three Pilllars)
• Have a solid foundation for easy improvements later on (like third-parties improvements). Because once the (scalable) GUI wallet will be there, we expect things to accelerate - and we rather be ready for the acceleration. Fasten your seatbelt, Dorothy.

Why is scalable important?
Because it is one of the three pillars

More seriously, because once the official GUI wallet will be there, visibility will increase a lot. Which means more users who know nothing about Monero and later not even about cryptocurrencies. These people won't give a second thought. One does only one first impression. It must be the right one. Hence the necessity for a wallet than can handle the load. Be scalable, not that much on a technical standpoint than on a, say, "political" standpoint.

We hope we answered your questions and, as always, don't hesitate to provide feedback. We'll do our best to make this even more clear if necessary.

This post was first published, in a slightly different version, as an answer to a commenter. Continue commenting, this is a great way to encourage us to write extensive replies!

Oh, one more thing: we do not have any release date for the GUI wallet, not even tentative. The only thing we can say is that the GUI wallet requires the database to be operational - and the database is progressing very well.

Update: some screenshots of the wallet some months ago:

• http://imgur.com/a/ERheR
• http://youtu.be/LlTDS3iCqRY?t=10m34s

hi,guys, I am sure I put paymentid in and withdrawal XMR from poloniex to bittrex. but bittrex said "NONE of my transactions have included a payment id ". Is that the truth ? would you please help me figure out the problem?

2015/2/3 12:35 XMR 1 463tWEBn5XZJSxLU6uLQnQ2iY9xuNcDbjLSjkn3XAXHCbLrTTErJrBWYgHJQyrCwkNgYvyV3z8zctJL PCZy24jvb3NiTcTJ txid: c4448f2bf8027fa0f38c97c20ef75d2f11cab8317769f01042f61be0eb317c04

So this sig-including doesn't work at all...

Yes, sorry, my question was phrased badly: where is development discussed? I mean, where could I go to find out the status of the RPC call implementation, or the often-discussed multisig stuff, or the db, etc? IRC? The Monero forum?

We haven't even started development on the new RPC API calls:)

With git you don't commit to the main repo every 5 minutes, that would make it exceedingly difficult to coordinate work between contributors. So developers work in their own forks and branches, and then submit pull requests to the upstream (main) repo.

Turns out, the calls from the Monero wiki are nowhere to be fund in the code on github.
No wonder I can't make it work, then.

Where is development happening? Not on github? There seems to be a very low activity...