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

Of course the bovine hordes have no idea what a ring signature is, much less how to use points on an eliptic curve to properly calculate a feasibly unbreakable key pair.

To be honest it is my opinion that most of the coven hoofed members of this forum could not even pick a good password.  My password, on the other hand, is so well picked I can tell you what it is and you will STILL not be able to access any of my 214 accounts here.  Actually I cannot access many of them anymore either, but that is a story for another post.

My password is the first and only multi dimensional mathematical representation of a singularity.  Not the one at the center of OUR galaxy as Sagitarius A would just be too obvious.

I am not worried about revealing that is is based on APM 08279+5255 as no hackers would be able to understand the gravitational algorithms I needed to calculate the checksum for my singularity model, and I believe if they even tried to hack my password the sheer weight of it's genius would cause them to go entirely mad.

I chose, for this reason, not to even change my password when this site was hacked.  But also because I am somewhat suspicious there would a devastating effect on the fabric of OUR universe if I WERE to change it.  Even my mistakes are so magnificent it is difficult to know what they are capable of.

Martin Armstrong wrote:


The emphasis, of course, is mine.

http://armstrongeconomics.com/archives/27578

I expect none of you are intelligent enough to understand this reasoning. (apart from possibly Smooth (though I am not certain of this as he has been somewhat resistant of my idea to rename his Aeon project into a particular Pygmy dialect that I am fond of (the pronunciation would be something like djanalaloa*CLICK*tasahee))).

I simply do not have time to try to teach cattle to read much less understand.

Good day.

https://getmonero.org/design-goals/

https://getmonero.org/2016/02/10/monero-missive-2015-year-in-review.html

Ring CT (and multisig) implementation is probably the most salient development -> https://lab.getmonero.org/pubs/MRL-0005.pdf

Can someone point me to the latest roadmap/results achieved?

And now for something completely different.

Does anyone play https://github.com/farin/JCloisterZone ?

If so toss me a pm when your up for a game. I generally play withing a group of 5 for the last 6 months a few times a week.

Ok, thanks for following up!

Your post has been forwarded to Shen, hopefully he'll able to answer you soon.

OK, I see why the double counting, it's a simple bug I think, I'll just have to make sure it doesn't have side effects before committing. There may be a bug with the missing tx too, will need some investigating.

The missing tx wasn't the first one, but rescan_bc helped insofar that the missing tx is now shown. BUT: the funny thing now is that each of the txs that were already shown previously by "show_transfers in" is now shown twice after I did rescan_bc.

The wallet was created with 0.8.8.6 iirc. Should I just make a new wallet with 0.9.1 and transfer everything there to be sure there are no inconcistencies?
I wouldn't have the transfer history though in the new wallet, which I'd like to keep.

Thanks!

https://bitcointalksearch.org/topic/in-order-for-a-cryptocurrency-to-be-successful-in-5-years-time-it-must-have-1285787 People highly value privacy/anonymity but a few knows what ring signature is

Is this from sweep_dust ? If so, this is intended, as sweeping dust can result in a (comparatively) huge tx fee (though some want the actual message wording to change in that case).
If not, do you have set always-confirm-transfers enabled ? If so, that's the reason.
If not, that seems to be a bug.

I read Shnoe's expository on SDC's ring signature flaw with great interest. I have a couple of questions.


1. I noticed that the following equation discusses a hash function, but unlike other hash functions in the paper, it does not have a subscript.

https://i.imgur.com/y4bkTFF.png

From context this is a hash function that returns a point with unknown log, and that this was just a typo, correct?


2. I was curious about the form of Shnoe's following equation

https://i.imgur.com/gLEDHgB.png

It does not seem to agree with the cryptonote white paper, which provides a more complicated equation for ci

https://i.imgur.com/G1TJtNE.png

Whereas the cryptonote white paper would make sense in this context, Shnoe's form does not seem consistent with his final statement that this "proves that someone has actually signed the transaction, since the signer, knowing xi is able to solve alpha = si + cixi".

Guys,

Howard Chu (hyc) is the chief architect of OpenLDAP https://en.wikipedia.org/wiki/OpenLDAP. He invented LMDB http://symas.com/mdb/ as OpenLDAP backend database.

He is a talented developer. It will be great if he can contribute more on Monero code as a core team developer.

Earned contempt average is amount of contempt divided by innings pitched.

Contempt of court, on the other hand, is an NBA problem, not a MLB problem.

Destroying other people's substance, also known as liposuction, is a profitable enterprise.

small cosmetics, dont know if it matters now that the GUI is coming..

still:


with 9.1 official (trx on testnet)

cheers and hodl

Nice upgraded Network Pool Hashrate Distribution listings on MoneroHash including some detailed comments.  Thank you

https://monerohash.com/#network


As always they show Active Node Distribution.  These are the ones with high up time. 

https://monerohash.com/nodes-distribution.html

Putting the blockchain on smartphones will not be required certainly but it isn't something entirely avoid either. As computing is moving more and more to mobile platforms, if you don't have mobile nodes you won't have many nodes at all. And furthermore if you want the highest degree of privacy and security you have to run your own node.

It is already quite feasible to run a node on a smartphone as demonstrated by people running them on RPis which are significantly less powerful than current smartphone models. Also, the database and bandwidth are being optimized which will further reduce the footprint (along with the possibility of DB pruning features). The 2 minute block time change will reduce the overhead a bit too.

The info show_transfers uses was originally not stored by default, but was switched to be on by default later on. If this is the case, the missing tx would be the first one. Is the missing tx the first one ?

An interesting test is to also run rescan_bc from the wallet, and see it that fixes it. If it does, it's likely a bug in the handling of blockchain reorgs in the wallet.

http://nodebox.link/

iso should properly set up networking to 192.168.1.199

will only work on home networks with gateways 192.168.1.1

Hi, I just noticed that the amounts reported by the two simplewallet commands

1) "show_transfers in"
2) "incoming_transfers"

do not sum up to the same value. The second one sums to the same value as what "balance" says (I didn't have any outgoing transfers from this wallet),
while the first one is missing one transaction with two outputs.

I'd like to use the first of the to commands as it nicely groups the outputs of each transaction and tells me the block height as well,
but if it misses transactions I'll have to stick with the second one for now.

Anything that I should know? Is the "show_transfers" command kind of experimental?

Thanks!

MAAM #3 - Monero Ask Anything Monday:

https://www.reddit.com/r/Monero/comments/45tdaf/maam_3_monero_ask_anything_monday/