We're preparing for a v0.3.0.0 protocol upgrade (code name Dandy Dromedary) coming in ~14 days, set for block #363,000 which will introduce SECOR (uncle mining), CNFastv2 PoW variant, and multi-output Bulletproofs (https://github.com/masari-project/masari/releases/tag/v0.3.0.0 ) . Linux binaries are available now, and others will be available soon (including GUI wallets). If you use the web wallet at masariwallet.com , you don't need to do anything as it will already be updated. If you're a miner, you will need to be prepared for the new PoW variant which we'll provide guidelines for soon. If you're a pool operator, you will need to update your daemon and there will soon be instructions on how to prepare for the new PoW and adjust payouts for uncle rewards.
Due to this, We're considering a medium-term solution that will retain decentralization, where we are considering Boolberry's Wild Keccak (WK) PoW (https://boolberry.com/files/Block_Chain_Based_Proof_of_Work.pdf ). This design we have found is similar in many ways to ideas in our prior PoW design discussions, and is potentially something we can expand development on if integrated. Currently, only Boolberry and Purk (a fork of BBR) are under this PoW which gives it higher financial risk that permits us more time to research and develop a more permanent PoW.
Discussions on alternative medium-term PoW solutions included ones with highly available ASICs (i.e. SHA, Scrypt), PoWs that don't seem much affected by ASICs (Ethash), consideration of all CryptoNote variants as non-viable short-term solutions due to FPGA programmability (we would end up back to square 1), as well as recent relevant research that would be of value (https://github.com/tromp/cuckoo/blob/master/doc/cuckoo.pdf, https://www.docdroid.net/GYEk2YB/eval-mtp-argon2d-final.pdf)
If we were to go through with this, we would likely modify some components of WK, including but not limited to changes in PoW operations, an increase of the iteration count to increase difficulty, and a starting chain scratchpad size that is higher than known FPGAs memory limits: we would call this Fat Keccak, or FatKek for short (https://i.redd.it/0mk07wzuahny.jpg ).
This is a summary initial report that was collaborated by members of the Core team as well as other community members such as @josef, @kacamak, and @dubz.
Further feedback is much appreciated and encouraged!
Today we've successfully forked our testnet to v8 featuring our new original design and implementation of what we'll be calling the SECOR (Simple Extended Consensus Resolution) protocol, delivering Uncle Mining that will increase network security, deliver faster blocks, and reward miners for their hard work that would've otherwise been orphaned. This blockchain advancement feature is cutting edge and a first in the CryptoNote space, and as such we need your help to review our work: bounties of up to 10,000 MSR (100 MSR minimum, depending on the severity of the finding) will be handed out for each new vulnerability discovered in our SECOR uncle mining design and implementation - I'll be publishing a whitepaper on SECOR to help with this peer review process.
[ANN-ES] [POW] [MSR] Masari - simple, escalable y seguro cryptocurrency
by
thaer
on 02/07/2018, 20:02:06 UTC
Masari (MSR) es una criptomoneda basada en Monero y centrada en la escalabilidad y en asegurar la privacidad.
Uno de los primeros aportes de importancia es la actualización necesaria para implementar uno de los algoritmos de dificultad más conocidos, cuyo objetivo es mitigar los problemas de flash mining al ser una altcoin de reciente creación. MSR rastreará la mayoría de los cambios hechos por Monero, y también contribuirá de vuelta siempre que sea posible (como con el algoritmo de ajuste de dificultad WHM). En el futuro se incluirán características como el minado de uncles (usando el protocolo DECOR+) y un whitepaper aún pendiente sobre un protocolo Blocktree que tiene como objetivo resolver la escalabilidad on-chain.
Especificaciones:
Algoritmo PoW: CryptoNight Fast Suministro máximo: ~18,5 millones (con tail emission) Recompensa de bloque: Relación de recurrencia suavemente variable que empieza en torno a 35 MSR por bloque, recompensa_bloque(altura_bloque)= (2^64 - 1 - suministro_total(altura_bloque - 1)) * 2 ^ -19 * 10 ^ -12 Tiempo entre bloques: 120 segundos Dificultad: Se reajusta en cada bloque Bloque de origen: Sábado 2 de Septiembre de 2017, 21:20:46 UTC
after fork change algo yesterday why diff aka nethash still so high where is the source come from ? i see global nethash about 16Mhs and then every pool not more than 1Mhs who is the robber ?
We just experienced a 23 block chain reorganization, a potential double spend attack on our network - everybody with buy orders on exchanges please pull out now until the exchanges respond with an audit of their databases!
What's up with the new windows CLI binaries. Brazen Badger seems to have issues every time I open it. I'm getting wierd symbols where letters are supposed to be.
[img removed]
Once the language is set I'm getting this error aswell.
[img removed]
The daemon seems to working fine however. Anyone else seeings these errors?
This is the first case I'm seeing, what block is your daemon synced at?
I had the problem that the v0.2.0.2 masari-wallet-cli would simply not recognize the wallet files from v0.1.4.0 as if there is no backward compatibility. You input the wallet password and get some error: "Error: failed to load wallet: std::bad_alloc"
So I used --restore-deterministic-wallet and entered the seed from the old wallet, but... attention... it will then ask you for something like a seed encryption pasphrase. If you enter one, it will generate a completely new seed with a new address, i.e. a new wallter, not your old wallet. I don't remember if this seed encryption passphrase was there in previous versions, well at least I didn't use it. So I had to restore again, this time leaving that seed encryption passphrase blank and so it finally restored my old address, i.e. exactly my old wallet.
That's on Ubuntu 16.04 LTS. Not tried the Windows or MacOS version.
If you rename your keys file (i.e. wallet-name.keys), it will solve the problem. This is because you have to clear your wallet cache (which would be wallet-name, no extension). A rename of the keys file instead of deleting the cache is the safest option (in case you accidentally delete your private key)
ASICs are a touchy subject, but we shouldn't be fighting over MSR's upcoming PoW change. The problem with CryptoNote ASICs is the centralization portion, not that it's an ASIC necessarily. In the current climate, this would mean that basically two companies (as of this writing) would dominate the hardware market for those kind of coins, and is a bad form of centralization with arguable defensible positions.
Monero's current thoughts regarding ASICs is in the long term to commit to a specific PoW that will be integrated in lets say 2 years time (while committing to PoW variants on each fork until then), which would give fair market competition to develop ASICs, and not cause centralized "secret" mining as what happened with Bitmain. The Masari community is indifferent to this position, since it may be conceded that ASICs (or FPGAs at the very minimum) are inevitable and only measures are needed to ensure decentralization. However, we may diverge from this and include in our roadmap research on an entirely new ASIC/FPGA-resistant PoW if deemed necessary.
@Cryptomaxsun I've seen you comment and discuss on this forum since early days. Putting the ASIC flame war aside (which includes other people), I'm confused why you'd resort to throwing ad hominems at the community (falsely saying it's not intelligent) and misrepresenting the roadmap (since we have clear reachable goals in the horizon, publicly shown on the home page https://getmasari.org/ ).
Good discourse on here is promoted, and there is always good discourse happening at our Discord, which everybody is welcome to join (https://discord.gg/sMCwMqs ).
The Vicex exchange banned us for "cheating" after we surfaced concerns about a security flaw in their database (plain-text passwords).
The Masari community is in agreement to avoid this one, and I recommend anybody who has made an account there with a reused password to immediately change their password where needed.
@romankosoj and Fonero troll army, sorry to burst your bubble but you're not fooling anybody here. You got to post some links on Fonero, good for you.
If you'd like to keep posting here so that this forum is constantly on the front page, you might be doing yourself a disservice by promoting Masari that way.
I don't get what the deal is with these Fonero trolls. Fonero repo's already been taken down for DMCA violation, both on GitHub and Bitbucket, and romankosoj recreated it again in GitHub as a fork of Monero then copy/pasted Masari's changes at the time of your fork onto it (commit 199ddfe05acc23f35b39171c1a13353a1fcbd7f2).
I left the Fonero project alone as an injured puppy, because the point was made clear that Fonero is a Masari fork that failed and refused to properly retain copyright, and they're unable to separate Masari's changes from Monero's because Fonero's incapable of doing so without breaking their network.
romankosoj has just about the foulest mouth I've ever come across, and doesn't know when to give up on his blatant lies and ad hominems. Why go through all this mess, just to avoid crediting copyright where it's due?
So far, only your words are dirty. Do u have any proofs except for commit from fonero repo? More than that I have information that you are manipulating themasari course, can u answer for this?
I've already gone through this headache, take a look at the Fonero forum page, there's plenty of evidence in screenshots and links from that time, even a screenshot of romankosoj himself admitting it to me in a DM that Fonero is a Masari fork and he will retain copyright where it's due (surprise, he didn't).
I don't get what the deal is with these Fonero trolls. Fonero repo's already been taken down for DMCA violation, both on GitHub and Bitbucket, and romankosoj recreated it again in GitHub as a fork of Monero then copy/pasted Masari's changes at the time of your fork onto it (commit 199ddfe05acc23f35b39171c1a13353a1fcbd7f2).
I left the Fonero project alone as an injured puppy, because the point was made clear that Fonero is a Masari fork that failed and refused to properly retain copyright, and they're unable to separate Masari's changes from Monero's because Fonero's incapable of doing so without breaking their network.
romankosoj has just about the foulest mouth I've ever come across, and doesn't know when to give up on his blatant lies and ad hominems. Why go through all this mess, just to avoid crediting copyright where it's due?
Basically the problem is that the Masari code has indeed modified the copyright statement which does not show the original Monero copyright. Also is suggest that you do not add Masari copyright to files which havent any real contributions by Masari except for function/variable name changes. This always bothered me, i had noticed this in Sumokoin then too.
I suggest looking at some other project (linux kernel my fav) to see how copyright assignments are done for new modifications. It better to rectify now than later.
I've made it more explicit in the repo earlier today when I saw what happened with Sumokoin, though it seems that they also didn't put it explicitly in the Readme which was likely the "last straw" (and I believe they got notice before this takedown at least a couple weeks ago?). There was a fairly significant refactor that occurred for Masari which touches a lot of the files, so selectively assigning Masari's notice on those files at this point would need more due rigour - I will do this at some point (I agree with your sentiment), despite being currently compliant with the BSD license.
What is the point to Masari? What does it improve on Monero?
The thing that Masari has implemented compared to Monero is a new DAA that could now be added to Monero (https://github.com/monero-project/monero/pull/2887). The plans for the future from what has been promised will be about on-chain scalability. The point is that Masari wants to contribute to the development of Monero where some things I think can't be tested directly, and provide a fork of Monero stable and maintained over time
Why even create a new coin fork when all you need is a test net?
I'm not here to convince you lol This is a fork of Monero and will take the road he wants . otherwise according to your reasoning we will not even talking about monero (fork of bytecoin) now
What? I asked a simple question, you make no sense and I see no direct answer to my question. Makes me think twice about putting BTC towards a test net for Monero.
I'm not the developer, put your btc wherever you want. The rodmap is on the website, it is not a simple test net, dyor
Part of "do your own research" is coming to a place where the developer frequents and ask questions which are not found anywhere else.
Masari is not even listed on coinmarketcap, so now can someone answer the simple question of what is the purpose of this Monero fork?
Hello,
Masari is an experimental coin with its goals not intended to compete with Monero, as they don't really overlap in objectives.
Masari's most recent improvement however does overlap, and surfaced exactly because of adversarial market effects on Masari's existence and not due to randomly fiddling with a testnet, seen in the pull request above, replacing an inefficient difficulty algorithm implementation in Monero.
The purpose of Masari is for on-chain scalability initiatives that have not been delved into in the CryptoNote space, starting with uncle mining using a variant of the DECOR+ protocol, followed by research into sharding/partitioning potential of the transaction outputs into a "blocktree" structure (pending a whitepaper draft and peer review).
Although there will likely be more upstream contributions (bug fixes, minor features, etc.), these goals differ greatly from Monero's as its team pursues 2nd layer solutions. I'm not one to say that on-chain scalability is a better pursuit, nor whether or not 2nd layer solutions are the best, and we're seeing new innovations coming out all the time that may take market dominance in the future (i.e. blockchain alternatives like Hashgraph, Raiblocks, IOTA, etc., ignoring decentralization concerns.).
I'd like to re-iterate that this is an experimental coin, with value outside of just being a local testnet, and for all intensive purposes is not necessarily intended to be one for you to invest in - there is little to no marketing here outside of organic community growth.