Many birthdays.
Much props.
So respect.
Wownero still alive at first bday?!?!!!??
|
|
|
Working. Thanks! Hopefully, wowlight gets an update as well cuz I've been having withdrawal symptoms from its cute snarky animation and chitty color scheme. I need a fix ASAP. soon^tm
|
|
|
MFW I'm reading the proof of work GitHub thread:
|
|
|
Keep getting this error while trying to send some WOW from Windows CLI wallet (last one for sure) to TO,
Error: Failed to find a way to create transactions. This is usually due to dust which is so small it cannot pay for itself in fees, or trying to send more money than the unlocked balance, or not leaving enough for fees
Maybe can you run with higher log level to get more info. Also, I think wowario maybe said something like this was fixed in upcoming 0.5.1.1, so maybe try to make an issue on GitHub repository as I think he follows that more closely than this thread.
|
|
|
Anyone used these guys yet? Deposits and withdrawals of more than a few dollars? Any complaints?
|
|
|
Briefly met the boss Jake at OKcoin hq in SF tonight. Supposedly some big Decred announcement tomorrow, and then Decred/USD pair listing on OKcoin on Thursday. Just heads up, but don't let the secret out please
|
|
|
In that discussion, as I've understood, sech1 focuses on the problem to make ASICs as efficient and as complicated as Intel CPU. linzhi-sonia says it will try because he likes this stuff with ASICs and their developing. What I think? We should focus on TRUE randomness instead of making mining algo to be too difficult for ASICs just because complicated design of the algo, for example, adding a true virtual machine level into algo design, like somewhat done in RandomX. Currently, cn/r uses block height as a source of randomness. And as linzhi-sonia mentioned, he will just add an interpreter or pre-compiled parts to the algo, because block height is known in advance to the future. I propose to add TRUE random generator via external ORACLES (like oracles work in Ethereum contracts). Or, good source of true randomness is LONG hash of all the transactions in last 100 blocks for example. Thus linzhi-sonia can't predict and pre-compile no parts of mining algo. Also we may dream about FLOATING POINT mining algo based on fining solutions of differential or integral equations of random nature. Finally we may focus on solution findings of SYMBOLIC mathematical problems, randomly generated. What do you think, Community? There's an active issue thread on GitHub discussing options for PoW moving forward: https://github.com/monero-project/meta/issues/316
|
|
|
When will you launch it??
We going to launch first public test net in January and then if stress tests passed well then we gonna launch production in Feb Dear friend When will BBR holders can swap from BBR to Zano? The conversion rate is 1:1 or ... and how long it takes! My friend, as long as nobody knows the amount of created zoin coins, any specific conversion rate does not make any sense. If the distributed number of zoin coins is around the number of bbr coins, then it makes sense, but nobody knows. I just wonder why do people talk here about Zoin?
|
|
|
...
I don't support ASICs on cryptonight nor arbitrary changes to this or that algorithm with no useful properties of its own but intended to give temporary advantage to GPU miners for some limited period after a switch.
Isn't that all of the modifications to cryptonight so far in a nutshell?
|
|
|
...
FWIW, I just tried it on a W10 x64 device...same thing.
Did you try building in msys or just running binaries already posted? The same downloaded latest binary I attempted to run on W7. I was hoping the daemon would work on W10 so I could sync and update my blockchain files. Ok, I'm gonna try to rebuild win bins on a different machine tonight or tomorrow, and if they still don't work I'll start working thru debug stuff with gdb.
|
|
|
...
FWIW, I just tried it on a W10 x64 device...same thing.
Did you try building in msys or just running binaries already posted?
|
|
|
I think no, because when you use a remote node you are allowing the remote daemon to select the other ring members for your tx, so a malicious remote node could determine your real tx output, and also link that to your IP if you weren't using a VPN or something. I think your best bet for privacy is to use your own daemon and broadcast the tx over Tor. (Disclaimer: I'm not a privacy geek and haven't actually done any of these things except use a remote node.)
Are ring members chosen by the daemon, not the wallet? How can you select other dummy tx outputs to use in ring signature if you don't have a copy of the blockchain containing other tx outputs? I'm fairly certain yes, the wallet requests ring members and the daemon returns them.
|
|
|
I was reading the ' Satoshi Roundtable V Recap' by Jameson Lopp. Interesting read. One part got me thinking about how it applies to Monero. It is generally said that running your own Monero node gives you the best privacy. But don't you actually give away more information broadcasting a transaction from an own node, over using a remote node? ... I think no, because when you use a remote node you are allowing the remote daemon to select the other ring members for your tx, so a malicious remote node could determine your real tx output, and also link that to your IP if you weren't using a VPN or something. I think your best bet for privacy is to use your own daemon and broadcast the tx over Tor. (Disclaimer: I'm not a privacy geek and haven't actually done any of these things except use a remote node.)
|
|
|
Crashes on W7 x64. Yeah I just uploaded it to someone else to try it. Will try to get it sorted today or tomorrow. Assuming the fork had already occurred, will there be a point release soon? The fork hasn't occurred yet, looking like Saturday maybe. I tried building master branch of Monero and had the same issue. I need to look at log output file and/or nuke my whole msys install and try again, but I just haven't had chance yet. Maybe tonight will mess with it.
|
|
|
|