There are no tools that implement the view key. We know it does work as it is used by the back end of MyMonero. I think luigi1111 said he was working on something, maybe others too. I guess I still don't understand. Why would Riccardo put the view key there, if it takes some specialized knowledge/setup to use it? I would rather that is not really advertised if it doesn't work and can't even be tested in at least simplewallet for instance. I see it as more like a sign of good faith I guess. "When this is implemented in a better fashion you'll be able to see the funds we receive and have received." |
|
|
|
There are no tools that implement the view key. We know it does work as it is used by the back end of MyMonero. I think luigi1111 said he was working on something, maybe others too. I have the ability to take an output and tracking key and get a simple answer on whether they match. I'm working towards extending that functionality a bit. I didn't get to work on it all today though.  Scanning the entire output set with a tracking key is beyond the scope of what I set out to do and has a massive computational cost. I need to think about it some more. |
|
|
|
no one living in some vanilla jurisdiction and wants to start a xmr dice/casino service? btw xmr and me are celebrating first wedding day today - not the easiest marriage but you know what people tell about feisty marriages  safedice will be offering the possibility to play/invest xmr "soon". can't give you any eta, since I'm not the one coding. additionally there is still the question how the cold wallet will be handled or better how to proof the reserves claimed (since there is no viewkey implementation yet). I didnt really like the workaround ccd used, so happy to hear any better ideas. I already have an idea, but it is not perfect given the jurisdiction I'm located at. Please note: I'm neither running nor owning the site. I was/am just an early investor who convinced the admin to go down the xmr route. I have a rough version of viewkey working (by individual output only at the moment). I'm still working out some (a lot) of the finer details. I thought onemorexmr had a viewkey thing working. It was incredibly slow - he forked it from someone else in #monero-dev. No idea. I'm not trying to create something that scans the entire blockchain for outputs (that's a job for Simplewallet), rather selectively decodes by output (and soon by TX) on an offline basis, using information from the block explorers for example. |
|
|
|
no one living in some vanilla jurisdiction and wants to start a xmr dice/casino service? btw xmr and me are celebrating first wedding day today - not the easiest marriage but you know what people tell about feisty marriages safedice will be offering the possibility to play/invest xmr "soon". can't give you any eta, since I'm not the one coding. additionally there is still the question how the cold wallet will be handled or better how to proof the reserves claimed (since there is no viewkey implementation yet). I didnt really like the workaround ccd used, so happy to hear any better ideas. I already have an idea, but it is not perfect given the jurisdiction I'm located at. Please note: I'm neither running nor owning the site. I was/am just an early investor who convinced the admin to go down the xmr route. I have a rough version of viewkey working (by individual output only at the moment). I'm still working out some (a lot) of the finer details. |
|
|
|
Thanks. On your last sentence, I'm not sure if I was clear: the base58 version is above in the code section "Integrated Address". That would be the version you'd actually use. The hex version at the bottom was for explanation only.
Thanks for the clarification, I didn't notice the distinction. That is great work. I nominate luigi1111 to get part of the bounties for designing this, the rest to go to whoever implements it (could be him of course). I agree. luigi1111 will definitely receive some XMR from me when this is implemented. However, I still pledge 100 XMR to whoever makes it happen. agree I'll send half of my bounty to luigi, if he provides me with an adress. Thanks. On your last sentence, I'm not sure if I was clear: the base58 version is above in the code section "Integrated Address". That would be the version you'd actually use. The hex version at the bottom was for explanation only.
Thanks for the clarification, I didn't notice the distinction. That is great work. I nominate luigi1111 to get part of the bounties for designing this, the rest to go to whoever implements it (could be him of course). I agree. luigi1111 will definitely receive some XMR from me when this is implemented. However, I still pledge 100 XMR to whoever makes it happen. Wow, you guys are far too kind! I've been thinking about this a bit more regarding solving edge cases, etc. I may have more ideas/details later. |
|
|
|
I don't remember who stated it above, but I do agree that the lack of exchange/merchant adoption might have something to do with the hassle of depending on users to include payment IDs.
Pay ID serialisation into the receiving address looks pretty far down on the roadmap. In the meantime, is there a reason why Payment IDs can't simply be appended to the address and parsed automatically by the client? That would make it much easier for third parties to manage payments until "stealth" payment IDs eventually get implemented.
No checksum is one reason why this will potentially backfire. That and the payment ID space is unnecessarily huge. I'll take a look at my notes from the MRL meetup in November last year, we had some ideas about fixing the payment ID format and serialising it, there may be a quick win to be had whilst we chip away at the stealth payment IDs. <snip> Adding the payment ID with checksum seems fairly simple. I went and created a test address just now: Standard Address: 44sKiMHpNjRivdd2NQUyViGYZy4wbJ9L9KhFUaqSSE6JQP9LLbxL9tSikwrhYTRu3x2zKR28txuEc3zSGPduQ9byMUKoz6m
Payment ID: feedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed Integrated Address: 44sKiMHpNjRivdd2NQUyViGYZy4wbJ9L9KhFUaqSSE6JQP9LLbxL9tSikwrhYTRu3x2zKR28txuEc3zSGPduQ9byXSb563RKvyBgorjsFGwyx9gorjsFGwyx9gorjsFGwyx9TpPbbCy What I did: Instead of the standard hex format - ('12' network byte) + (public spend key 64 digits) + (public view key 64 digits) + (checksum 8 digits) - I stripped the checksum and appended the payment ID, then recalculated and appended the new checksum. This creates a 101 byte address instead of the standard 69 byte, and 139 "Public Address" characters vs 95 standard. cnBase58 --> hex the above "Integrated Address" and you get (separated for clarity): 12 55a1e49673f5a8faa6ba4f942585695ceee5c7522496be6fc38d3f09905e3f8b ca6313deac11aff9a7241e7095863b0be3099d50d7a0cd11e0adbcf4990e64b5 feedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed b1d0950e The code just needs to check for length to determine the type. Alternatively, (I don't know what all the other cryptonotes are using) the network byte could be changed to 0x13 or something for the "Integrated Address". Looks very nice. Something like this seems like the way to go, especially in that it can be recognized as a different address type. You can shorten the pid (and the whole thing) by converting it to base58 instead of hex. Thanks. On your last sentence, I'm not sure if I was clear: the base58 version is above in the code section "Integrated Address". That would be the version you'd actually use. The hex version at the bottom was for explanation only. |
|
|
|
I don't remember who stated it above, but I do agree that the lack of exchange/merchant adoption might have something to do with the hassle of depending on users to include payment IDs.
Pay ID serialisation into the receiving address looks pretty far down on the roadmap. In the meantime, is there a reason why Payment IDs can't simply be appended to the address and parsed automatically by the client? That would make it much easier for third parties to manage payments until "stealth" payment IDs eventually get implemented.
No checksum is one reason why this will potentially backfire. That and the payment ID space is unnecessarily huge. I'll take a look at my notes from the MRL meetup in November last year, we had some ideas about fixing the payment ID format and serialising it, there may be a quick win to be had whilst we chip away at the stealth payment IDs. I disagree that we need to do nothing while we work on something better (obviously one does not preclude the other at all). There is no checksum now. The length and valid characters are checked but that's it. The exact same thing can still be checked if the format is changed, slightly to something like Send to this address: 46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8aHYjA3jk3o1Bv16em-e981847d2b9e1860d56bcb2263864db976d52e88c9c97db5e734d204f06bedac Instead of Send to this address: 46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8aHYjA3jk3o1Bv16em
and use this payment ID
e981847d2b9e1860d56bcb2263864db976d52e88c9c97db5e734d204f06bedac
Adding the payment ID with checksum seems fairly simple. I went and created a test address just now: Standard Address: 44sKiMHpNjRivdd2NQUyViGYZy4wbJ9L9KhFUaqSSE6JQP9LLbxL9tSikwrhYTRu3x2zKR28txuEc3zSGPduQ9byMUKoz6m
Payment ID: feedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed Integrated Address: 44sKiMHpNjRivdd2NQUyViGYZy4wbJ9L9KhFUaqSSE6JQP9LLbxL9tSikwrhYTRu3x2zKR28txuEc3zSGPduQ9byXSb563RKvyBgorjsFGwyx9gorjsFGwyx9gorjsFGwyx9TpPbbCy What I did: Instead of the standard hex format - ('12' network byte) + (public spend key 64 digits) + (public view key 64 digits) + (checksum 8 digits) - I stripped the checksum and appended the payment ID, then recalculated and appended the new checksum. This creates a 101 byte address instead of the standard 69 byte, and 139 "Public Address" characters vs 95 standard. cnBase58 --> hex the above "Integrated Address" and you get (separated for clarity): 12 55a1e49673f5a8faa6ba4f942585695ceee5c7522496be6fc38d3f09905e3f8b ca6313deac11aff9a7241e7095863b0be3099d50d7a0cd11e0adbcf4990e64b5 feedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed b1d0950e The code just needs to check for length to determine the type. Alternatively, (I don't know what all the other cryptonotes are using) the network byte could be changed to 0x13 or something for the "Integrated Address". |
|
|
|
Deleted rangedriver's and elripp's replies that both quoted BlockaFett's post but added no meaningful content
So far freedom of speach goes down the drain in this forum  The fact that BlockaFett's quoting is meaningful in your opinion, does not really raise my cocnitive aspiration. Maybe you should consider not beeing so bullish towards your supporters.... You overshot this one pretty clearly smooth  elrippo I have nothing against your contributions but when you quote 50 lines and then add one line that doesn't actually say anything, I'm sure you can do better. smooth, cool down, take a good cup of tea and let me say what i want to, when i want to. I don't charge you for your words, so please do not charge mine. "quit pro quo" It's "quid pro quo", and this thread is moderated, with clear-ish rules laid out in the OP. It is smooth's prerogative to moderate it how he sees fit. Being a supporter has no bearing on your entitlement to post off-topic stuff. Note: I didn't read either of the posts that got deleted, so this isn't directed at what either of you said. It's just how things should work in general. Off topic posts will be removed. Off topic includes any extensive discussion of other coins, promoting other coins, or posting of promotional materials from other coins.
Non-substantive comments such as Monero sucks, Monero is a scam, Monero is great, Monero to the moon, etc. are considered off topic. Every post and reply should add to the discussion. If smooth doesn't remove OT posts, then he's somewhat of a liar (keeping in mind post quality is often subjective). |
|
|
|
I've been a large and long term holder of Monero up until this week, approx this time last year my XMR holdings were worth $60,000 and I've sold none until now, why did I decide to sell - because I took a good long look at the coin, it's development and potential as far as I could see it and decided that it was no longer something that I wished to support. Why did I take a fresh look at it, because among other coins that I back is DASH and on the BCT DASH thread there is constant trolling by Monero fans and the dev smooth, just check how many posts he's made there today alone, dozens and dozens and dozens, why is this happening - I assume to make the thread unreadable and spread FUD, well it does this but it also creates a very poor image of crypto in general and Monero in particular, it is going out of one's way to try and antagonize everyone who sees it. So I am no longer prepared to back a coin that has a main dev act in such a toxic way, I now no longer own any and do not plan to in the future, those remaining I wish you well with it but my decision to sell three days ago was primarily a business one, I do not see a bright future for this coin as things are atm I'm sorry to say.  I feel your pain. The entire dev team is behind the DASH FUD campaign. They chose smooth to carry the attack because he has nothing to lose, his reputation in this thread was lost months ago. Inspired by Otoh's brave example, I also have decided to sell all my XMR. I use the Dark Theme on Poloniex because I'm cool. As you can see, this is me selling everything. As you can see from the screenshot I'm selling my 192382374923412.203874 XMR for 384782064260.56750488 BTC (around $86.19 trillion). Hopefully the market can sustain this dump.  In future I look forward to teleporting you all to my private island on the planet Neptune, where we can fly our hovercars around and laugh about the good ol' days. You moron doofus, you forgot to blank the stop limit section.  Edit: oh you fixed it, now I'm the doofus. Edit2: I'll have you know there's only one of me! |
|
|
|
Here we go: Address: 42aaBurnXMRBurnBurnXMRBurnBurnXMRBurnBurnXMR13DXCDQWwCATBednqL7EKiXejT55RDHdzPC mxid66QRLMugnw2G Viewkey: 1ac191890bc6ae9fe3a8115e83263abce1f020144ee7e5254e14efb9dcea8105 I have tested the "burn" functionality by sending a small amount to this address (it's quite a rush, give it a try  ). Here is my TX: http://www.chainradar.com/xmr/transaction/3304656a4891542b9e350762c609affba76a6de1c8c1991a81a009bf513f5bcc (take note of my payment ID ) Now, I cannot vouch for the "auditability" of this address, though the viewkey above is certainly valid, and I promise no one will be able to spend any funds that are sent here. I was curious to see if anyone else had burned their XMR already... sadly not  only your transaction of 0.1XMR there. Probably to verify the burn the paymentId and amount could be treated as the secret the user must use to prove they were the one to burn their XMR. Though why not just send them to donate@getmonero.org in that case? Burning FIAT is kind of illegal, it should be illegal to burn Moneros as well Well you wouldn't be able to tell because of stealth addresses anyway, unless they copied my payment ID. And they could just do that to pretend while actually sending to themselves. It's not too difficult to prove you sent the TX, as you own the private key for it (just needs implemented). The auditing needs implemented on the other side to verify that the burned funds are actually arriving in the account. I desire to set up a website capable of doing just this (for another purpose, but this would be a fun "extra" piece). But yes, the feeling of pressing "send" is quite a rush; adrenaline junkies, go! We could burn small amounts while being creative with the payment IDs, then when the auditing is set up, all the TX's could be grouped with the IDs for comedic effect. I figured out how to selectively audit this transaction (or the 0.1 output at least), proving it went to the burn address. Pretty cool stuff. |
|
|
|
Are there outside branches from the main github that I should be following to see what's being progressed on. Master hasn't had any new commits since the db merge and the development branch there is so old. I'm not really sure who's doing what.
Yes, you can check the forks and contributors pages on github to track them down. Further, are the missives still going on? The last one is like a month old, just curious if these updates have stopped or if we can expect them to continue again in the near future.
GingerAle, you're up. (I don't know.) Fluffypony, you're up. (snarf) - I'm not trying to pass the buck, but the current SOP has me editing them, and then transferring to fluffy, and he uploads to the server. Him and I are trying to find a way to remove him as the middle man in terms of final upload, but still weigh in on editorial decisions, because if I had my druthers ... well lets just say I have a strange sense of humor sometimes. So eventually I'll send him an MP3 and he'll go "ja" and then I'll upload or he'll say "noer" and i'll go through and edit out the section where I babble incoherently for 10 minutes about multidimensional geometric data compression algorithms. But unfortunately finding a new SOP involves a tele-sitdown, and our schedules have been bolloxed. Look, its not my fault that the sun moves around the earth and everyone thinks their local time should correspond to the local diurnal cycle, as opposed to synchronizing their clocks to US eastern. You are almost right, US central is the actual zone. |
|
|
|
I don't think the GUI is the key. Monero appeals most to extremely intelligent people who also have lots of money (aminorex, ArticMine). This type of guys will be the deciders of the price in the short (1 year) term. The masses come later.
I should refocus to the MiG thing. That is directing to the above segment. Here, my laborious scenario analyses did not receive even one comment. That is indicative that you aren't even interested in Monero here! We need more leaders, and we are bound to get them on board in the coming months.
Just so you know, I read and enjoyed everything you wrote on the subject, but did not feel an immediate need to make any comments. I feel confident there are many others like me. Perhaps we should be more expressive.  |
|
|
|
[words]
From a pure hedge perspective, excluding all the non-POW coins, XMR built from a different codebase makes sense. There is nothing wrong with clones of Bitcoin's codebase (until there is). There really isn't another player in the cryptonote space that makes a viable hedge. Just a sea of anemic (or dead) projects. Bytecoin isn't viable due to distribution and I think that's reflective of lack of trading volume on top of little exchange exposure.
Full disclosure, I own both Dash and Monero. This isn't a post to start the debate up between either again. It's still far too early to even declare a winner but I have always stated that the privacy niche and fungability of crypto is of the utmost importance.
Finally, there are really two primary events that could happen in the POW altcoin world that could spark massive flows, excluding Bitcoin-related scenarios:
1. The first POW coin to overtake LTC's positioning as second to BTC (only a matter of time IMHO).
2. The first privacy-centric coin to overtake Dash/Darkcoin (not saying this will or won't be the case, but the title has long been in the DRK/DASH camp and it will certainly be mentioned repeatedly should another coin overtake it).
There is a lot of "dead" money tied up in Litecoin that could be repurposed.
Good post. I agree that XMR makes a suitable hedge for several different purposes. That "suitable" label actually makes it quite unique IMO. This last tirade of gibberish has found you on my ignore list truecraptonaire. You need to ease up on the bs and add some substance.
TC is pretty easy to read, actually I'm pretty sure it's purposely done. You see, TC is in buying mode right now. Not when it's cheaper. I distinctly remember the good old trollbox days in the first half of last year when there were no less than three or four flip flops a day on whether or not Monero was going down or up, based on whether or not TC was buying or selling. Personally, I find the mannerism so transparent that I've disregarded it as bs. Right here: Funny thing I do not even have any temptation to buy coins at these prices.
And I sold them long time ago, not today or yesterday.
And here: I am also doing other project so I don't have that much time for trolling here and of course, buying the coin.
Literally translates to me as: I sold Monero the day before yesterday, and am looking to buy back in Monero cheaper after I've gotten a small-medium gain on a poopcoin probably next week. Either way, I'll be able to buy more Monero next week after this turdcoin I'm buying pumps, but I'd rather buy Monero lower than when I sold it.
Personally, it just doesn't seem so offensive to me at least. I agree with this post, especially the last line. I do find the back and forth between him and several other members, well, hilarious. Goes well with my morning coffee.  |
|
|
|
where the heck is this xmr coming from that these whales keep dumping in massive bulk over and over and over again? changes in the price never seem to come from changes in sentiment from the general community, but the unilateral actions of whales. what is the cause of this? when does it end?
Infinite coin exploit confirmed. IS IT TRUE? |
|
|
|
what is considered a large stash of moneros these days?
I would consider anything above 25k moneroj quite large, but if you are a whale it may be nothing. u r whale ? lol I wish I was... i'm but a humble tuna. Im not even close to 25k btw less than 1000 ppl can ever own more than 25k moneroj in this century. This is very true, and really puts things in perspective. |
|
|
|
what is considered a large stash of moneros these days?
I would consider anything above 25k moneroj quite large, but if you are a whale it may be nothing. u r whale ? |
|
|
|
Here we go: Address: 42aaBurnXMRBurnBurnXMRBurnBurnXMRBurnBurnXMR13DXCDQWwCATBednqL7EKiXejT55RDHdzPC mxid66QRLMugnw2G Viewkey: 1ac191890bc6ae9fe3a8115e83263abce1f020144ee7e5254e14efb9dcea8105 I have tested the "burn" functionality by sending a small amount to this address (it's quite a rush, give it a try ). Here is my TX: http://www.chainradar.com/xmr/transaction/3304656a4891542b9e350762c609affba76a6de1c8c1991a81a009bf513f5bcc (take note of my payment ID ) Now, I cannot vouch for the "auditability" of this address, though the viewkey above is certainly valid, and I promise no one will be able to spend any funds that are sent here. I was curious to see if anyone else had burned their XMR already... sadly not only your transaction of 0.1XMR there. Probably to verify the burn the paymentId and amount could be treated as the secret the user must use to prove they were the one to burn their XMR. Though why not just send them to donate@getmonero.org in that case? Burning FIAT is kind of illegal, it should be illegal to burn Moneros as well Well you wouldn't be able to tell because of stealth addresses anyway, unless they copied my payment ID. And they could just do that to pretend while actually sending to themselves. It's not too difficult to prove you sent the TX, as you own the private key for it (just needs implemented). The auditing needs implemented on the other side to verify that the burned funds are actually arriving in the account. I desire to set up a website capable of doing just this (for another purpose, but this would be a fun "extra" piece). But yes, the feeling of pressing "send" is quite a rush; adrenaline junkies, go! We could burn small amounts while being creative with the payment IDs, then when the auditing is set up, all the TX's could be grouped with the IDs for comedic effect. |
|
|
|
if you have 2 addresses, one is a real address (with private key) and one burn address, then you can publish the viewkey of the first one and see all the transactions made from this address to the burn address.
Are you sure? I think what you would see as destination would be a stealth destination (maybe corresponding to the burn address, without any way to prove it). interesting. In order to test it what I need is this burn address I (with the "phone a friend" option) got this figured out. I will create the address today hopefully. Stay tuned! Here we go: Address: 42aaBurnXMRBurnBurnXMRBurnBurnXMRBurnBurnXMR13DXCDQWwCATBednqL7EKiXejT55RDHdzPC mxid66QRLMugnw2G Viewkey: 1ac191890bc6ae9fe3a8115e83263abce1f020144ee7e5254e14efb9dcea8105 I have tested the "burn" functionality by sending a small amount to this address (it's quite a rush, give it a try ). Here is my TX: http://www.chainradar.com/xmr/transaction/3304656a4891542b9e350762c609affba76a6de1c8c1991a81a009bf513f5bcc (take note of my payment ID ) Now, I cannot vouch for the "auditability" of this address, though the viewkey above is certainly valid, and I promise no one will be able to spend any funds that are sent here. Oh, the waste! Oh, the pity of it! http://moneroblocks.eu/search/feedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedHe must FEEEEEEEEED!! Though, one does not know how much I actually sent there, just that it was 1.99 or less. |
|
|
|
if you have 2 addresses, one is a real address (with private key) and one burn address, then you can publish the viewkey of the first one and see all the transactions made from this address to the burn address.
Are you sure? I think what you would see as destination would be a stealth destination (maybe corresponding to the burn address, without any way to prove it). interesting. In order to test it what I need is this burn address I (with the "phone a friend" option) got this figured out. I will create the address today hopefully. Stay tuned! Here we go: Address: 42aaBurnXMRBurnBurnXMRBurnBurnXMRBurnBurnXMR13DXCDQWwCATBednqL7EKiXejT55RDHdzPC mxid66QRLMugnw2G Viewkey: 1ac191890bc6ae9fe3a8115e83263abce1f020144ee7e5254e14efb9dcea8105 I have tested the "burn" functionality by sending a small amount to this address (it's quite a rush, give it a try ). Here is my TX: http://www.chainradar.com/xmr/transaction/3304656a4891542b9e350762c609affba76a6de1c8c1991a81a009bf513f5bcc (take note of my payment ID ) Now, I cannot vouch for the "auditability" of this address, though the viewkey above is certainly valid, and I promise no one will be able to spend any funds that are sent here. |
|
|
|
|
Show Posts
