[ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B

[SHossainKMD]

When the KMD dev sees a flaw in our code and chooses to exploit it, it's a problem. Do you think we intended for Komodo genesis notaries to be able to mine free coins? Was that our mistake, hell yes it was and it was a damn bad one because it turns out the KMD devs are not to be trusted.

Why do you so sure that was KMD dev team members mined your coin? Believe me, i wish your project only bright future and if you will implement in it something new and useful to the community, for example, new tech or another interest solution - it will be great. But, unfortunatelly, currently SAFE coin looks like scam. Why i think so? Let's look:

1. If it was serious long time project - devs never release this code with KMD notaries public keys inside. Have you heard anything about the stages of the software development life cycle? Before release every software should going through many checks, tests and this is months of hard work.
2. Unfortunatelly, we don't see any work here. SAFE coin devs just forked (i wish to call it "copy & paste", like in middle school) KMD sources, changed KMD strings on SAFE and tried to introduce it as new project. Do you think it's seriously? Will you deny that no one of devs has even tried to understand the essence of how this works? From side look like "devs" of SAFE don't tried to clarify for itselfs too much moments inside a code. Otherwise, they would have created their own notary.
3. Ok. Let's explain that SAFE is not one-day project, not scam ... what we have? Only copy & pasted sources and few screenshots in SAFE thread, which can be drawn in maximum per hour. Whitepaper? No. Official site - doesn't work. Explorer? Haven't.

What SAFE have you may asked? Only topic on this forum with a few screenshots, copy & pasted code, and ambitious statements and charges. Nothing more (currently).

p.s. About mining. Everybody could start safe coin daemon with one of notaries public key and mine SAFE. Also, everybody could start mining with all notaries_elected pubkeys. Why? For example, to show people this project is not serious, even if its developers do not understand how it works. Of course, if somebody mined SAFE with komodo's notaries pubkeys - he can't spent it without privkeys, but in order to show the incompetence of developers - this is enough.

1. Notaries were planned for a later stage, and yes the harmfulness of leaving those in the code, was overseen and your dev gladly used this error to snatch some coins - however he screwed that up and for the SAFE community it looked like a deliberate attack first (until clarification that is was meant to be 'only' a little coin grabbing activity)
2. SAFE is about 2 month old, how much new feastures do you expect in that short time frame from a small group of part-time devs? Please be realistic
3. There is a website (safecoin.org) , please check it out, there were two block explorers (before the fork) and overall the community was quite happy with the progress until your Dev fucked it all up during his lil' raid.

Safecoin is a scam coin. Created only for pump and dump. What kind of delusional brain deaded people blame others for their own mistake. What kind of idiot copy and paste source code and release without checking? Safecoin says it's dPOW, where is the proof?

Just go away you mean ill-minded trolls.

So, how they scammed anyone? There was not even one offer to buy or sell coins.
Please inform yourself before making any accusations. Thanks.

They are frauds,  if they dont have notaries and are not notarizing yet claim to be using DPoW

Actually who gives a Sh.. about this dPoW stuff for a coin that is not even listed on any market? Maybe our dev thought it KMD is a well advanced tech and did not expect this to be buggy as fuck.
Thas was his mistake in the first please, but does not shed a good light to KMD as well.

All these accounts trolling are newbie accounts. Only screams scam! Where you will be thankful and happy that a bug has been found, instead you are blaming for your own mistake. Do you also blame god for making you this way with some bugs in you? You copy-paste someone's code, you make mistake and blame others. Only means blind trolls.

[SlickRick]

When the KMD dev sees a flaw in our code and chooses to exploit it, it's a problem. Do you think we intended for Komodo genesis notaries to be able to mine free coins? Was that our mistake, hell yes it was and it was a damn bad one because it turns out the KMD devs are not to be trusted.

Why do you so sure that was KMD dev team members mined your coin? Believe me, i wish your project only bright future and if you will implement in it something new and useful to the community, for example, new tech or another interest solution - it will be great. But, unfortunatelly, currently SAFE coin looks like scam. Why i think so? Let's look:

1. If it was serious long time project - devs never release this code with KMD notaries public keys inside. Have you heard anything about the stages of the software development life cycle? Before release every software should going through many checks, tests and this is months of hard work.
2. Unfortunatelly, we don't see any work here. SAFE coin devs just forked (i wish to call it "copy & paste", like in middle school) KMD sources, changed KMD strings on SAFE and tried to introduce it as new project. Do you think it's seriously? Will you deny that no one of devs has even tried to understand the essence of how this works? From side look like "devs" of SAFE don't tried to clarify for itselfs too much moments inside a code. Otherwise, they would have created their own notary.
3. Ok. Let's explain that SAFE is not one-day project, not scam ... what we have? Only copy & pasted sources and few screenshots in SAFE thread, which can be drawn in maximum per hour. Whitepaper? No. Official site - doesn't work. Explorer? Haven't.

What SAFE have you may asked? Only topic on this forum with a few screenshots, copy & pasted code, and ambitious statements and charges. Nothing more (currently).

p.s. About mining. Everybody could start safe coin daemon with one of notaries public key and mine SAFE. Also, everybody could start mining with all notaries_elected pubkeys. Why? For example, to show people this project is not serious, even if its developers do not understand how it works. Of course, if somebody mined SAFE with komodo's notaries pubkeys - he can't spent it without privkeys, but in order to show the incompetence of developers - this is enough.

1. Notaries were planned for a later stage, and yes the harmfulness of leaving those in the code, was overseen and your dev gladly used this error to snatch some coins - however he screwed that up and for the SAFE community it looked like a deliberate attack first (until clarification that is was meant to be 'only' a little coin grabbing activity)
2. SAFE is about 2 month old, how much new feastures do you expect in that short time frame from a small group of part-time devs? Please be realistic
3. There is a website (safecoin.org) , please check it out, there were two block explorers (before the fork) and overall the community was quite happy with the progress until your Dev fucked it all up during his lil' raid.

Safecoin is a scam coin. Created only for pump and dump. What kind of delusional brain deaded people blame others for their own mistake. What kind of idiot copy and paste source code and release without checking? Safecoin says it's dPOW, where is the proof?

Just go away you mean ill-minded trolls.

So, how they scammed anyone? There was not even one offer to buy or sell coins.
Please inform yourself before making any accusations. Thanks.

They are frauds,  if they dont have notaries and are not notarizing yet claim to be using DPoW

Actually who gives a Sh.. about this dPoW stuff for a coin that is not even listed on any market? Maybe our dev thought it KMD is a well advanced tech and did not expect this to be buggy as fuck.
Thas was his mistake in the first please, but does not shed a good light to KMD as well.

All these accounts trolling are newbie accounts. Only screams scam! Where you will be thankful and happy that a bug has been found, instead you are blaming for your own mistake. Do you also blame god for making you this way with some bugs in you? You copy-paste someone's code, you make mistake and blame others. Only means blind trolls.

Look, I don't want to troll, but somehow discussions often end up like this, because there are two sides of the story.
Yes, I admit that our dev oversaw this vulnerability during the implementation but it was also not good behaviour to try to use this error to get greedy and fuck up the whole network instead of just informing the safe community that there might be vulnerabilities. I bet our dev would have given him much greater rewards than he was able to grab by himself.

I am done now, because I know I cannot convince anyone here and that is fine, but seeing the behaviour of the involved persons in the last few days (our community members and some of yours) I made my decision what is the more "ethical" way to go and which intensions were behind.
I wish your project all the best but if someone comes along and wants to build something new on your platform (in the spirit of open source) don't push them around as you did with us.

[Decker]

gfigg42, anyway - currently i see only words, like "we planned dPOW in future", "we will do ... ", "we will send people to Mars" ... in future ... may be ... But on Git - i see only copy&pasted code and bunch of "fixes", hasty attempts to correct mistakes of SAFE devs misunderstandings basics.

And all blames and insults here - don't look good and reduce your credibility among community, at least because these insults against creators of 99.999999999% of SAFE sources. It's better to don't waste time here on "bad words" and focus on your project.

[gfigg42]

gfigg42, anyway - currently i see only words, like "we planned dPOW in future", "we will do ... ", "we will send people to Mars" ... in future ... may be ... But on Git - i see only copy&pasted code and bunch of "fixes", hasty attempts to correct mistakes of SAFE devs misunderstandings basics.

And all blames and insults here - don't look good and reduce your credibility among community, at least because these insults against creators of 99.999999999% of SAFE sources. It's better to don't waste time here on "bad words" and focus on your project.

We were focused on our project until their little stunt blew up in both our faces. Since then we have been "focused" enough to accomplish a fork that KMD did not think we could manage. We've restarted our chain, and removed the notary node vulnerability. For now we function as a pure POW coin like 99.99% of the coins out there. Implementation of further features is common in forks and we fully intend to embrace dPoW but in our way. KMD wants new code? They just got some and they're going to see more. Is that enough "focus" for you?

Perhaps KMD could use some of this "focus" on their own coin instead of shitting on a tiny fork coin because they thought we weren't sufficiently bending the knee to our masters? How about some "focus" on what's important to their coin, not their overblown egos. We respect the KMD code or we wouldn't have undertaken this project. We believe it's the best there is or we wouldn't be here dealing with this bullshit.

There may be other vulnerabilities in our fork. We are not gods. Perhaps KMD would be kind enough to point them out to us instead of conspiring for new ways to exploit them?

[oblox]

gfigg42, anyway - currently i see only words, like "we planned dPOW in future", "we will do ... ", "we will send people to Mars" ... in future ... may be ... But on Git - i see only copy&pasted code and bunch of "fixes", hasty attempts to correct mistakes of SAFE devs misunderstandings basics.

And all blames and insults here - don't look good and reduce your credibility among community, at least because these insults against creators of 99.999999999% of SAFE sources. It's better to don't waste time here on "bad words" and focus on your project.

We were focused on our project until their little stunt blew up in both our faces. Since then we have been "focused" enough to accomplish a fork that KMD did not think we could manage. We've restarted our chain, and removed the notary node vulnerability. For now we function as a pure POW coin like 99.99% of the coins out there. Implementation of further features is common in forks and we fully intend to embrace dPoW but in our way. KMD wants new code? They just got some and they're going to see more. Is that enough "focus" for you?

Perhaps KMD could use some of this "focus" on their own coin instead of shitting on a tiny fork coin because they thought we weren't sufficiently bending the knee to our masters? How about some "focus" on what's important to their coin, not their overblown egos. We respect the KMD code or we wouldn't have undertaken this project. We believe it's the best there is or we wouldn't be here dealing with this bullshit.

There may be other vulnerabilities in our fork. We are not gods. Perhaps KMD would be kind enough to point them out to us instead of conspiring for new ways to exploit them?

Edit your thread then to reflect that you are, in fact, not using dPOW and NOT secured by Bitcoin. It's misleading otherwise.

[MoneyJ]

Notary nodes providers are in arms defending dPoW from a wannabee benefactor of the technology. Let him spread false hood that eventually nobody would ever believe his/her statements. Komodo is an open source software that anybody could replicate it but  without in-depth knowledge of this super complex dPoW architecture. The said copier will find it hard to implement.

[gfigg42]

Notary nodes providers are in arms defending dPoW from a wannabee benefactor of the technology. Let him spread false hood that eventually nobody would ever believe his/her statements. Komodo is an open source software that anybody could replicate it but  without in-depth knowledge of this super complex dPoW architecture. The said copier will find it hard to implement.

Bizarre. Where have I said anything negative about dPoW that would require anyone to defend dPoW? It's fantastic tech.

We accept the challenge. You can laugh if we fail.

[ComputerGenie]

...Where have I said anything negative about dPoW that would require anyone to defend dPoW?...

ummm....

patch malicious komodo dev team hack

https://github.com/Fair-Exchange/safecoin/commit/b0f7f211ba8738aad340662b9bfe9655c335446f

final removal of malicious KMD notary nodes

https://github.com/Fair-Exchange/safecoin/commit/e8fbb370d57314fc056d0d80978e526dd6226185

[CHMEX]

I would like to share today a report I made analyzing the usage of the KMD chain.

https://dexstats.info/docs/Komodo_Transactions.pdf


Usage is the most important factor of giving a network a specific value. KMD is currently at a trx count of ZEC (Zcash) and XMR (Monero).

With the increased usage of Barterdex the trx count will increase also by adding more notarized chains to the KMD ecosystem we will see more transactions which ultimately will increase the value of the Komodo Network.

[KomodoPlatform]

Step-by-step guide: How to vote a private Z-Address at the Notary Node Elections 2018

[SHossainKMD]

Komodo 2.0 in Simple Words
by jl777
25 March 2018

The security alone is enough to justify it as assetchains need to be secured, but now that it exists it turns out to enable smartchain combos where multiple smartchains can all be combined into a combined set of chains that are all able to validate consensus in the other chains, relying on the notarized MoM (Merkle root of Merkle) data.

KMD is the repository for all the MoM notarizations. So on the KMD chain (secured by BTC notarization) is a record of MoM that spans all the notarizing chains block's merkle roots.

Each block has a merkle root that allows for any txid in that block to be verified, given the merkle root and an SPV proof. So, if you have the raw txbytes, you can validate the txid and if you have the SPV proof, you can validate that the txid is in that block. This is standard SPV validation.

Take it one step further.

Now we have notarizations happening every so often. In each a MoM is added, which is the merkle root of merkle roots for all blocks from that notarization height backwards to the previous notarization. Just as you can verify that a txid was in a block, we can therefore verify that a block with a specific merkle root was notarized! So combine it with being able to validate any transaction happened in a specific merkle root and we get that we can validate that a specific transaction happened on a specific chain. And, it can be any chain that is notarized, and all this info is in the KMD chain.

Once you can comprehend the above, you will realize that this totally solves the scalability issue of smart contracts.

Without using some untested massively complex and hard to understand new tech. It builds on proven SPV validation. SBV I guess, simple block validation. Validate a tx happened in a block and validate that that specific block was notarized in a specific blockchain.

The other shoe that is needed to understand is that each smartchain can have one or more special evaluation functions that can be literally anything you can write code to validate. Can be about mutating kittens, or whether a certain address did a certain transaction, whatever can be coded into a true/false evaluation funtion. The CC (Crypto Contracts) script can be based on that.

So, we get BTC secured cross chain CC scripts with arbitrary chain specific evaluation functions. No sharding needed as all data for each smartchain only exists on that chain. So, while all the other platforms struggle to implement these crazy complicated whitepaper solutions, we are debugging the simple scaling solution.

The paper for it will be written after it is completed, but it wont be very long as it is building on notarization security, CC and SPV validation which already has a lot of history.

Well, already during implementation we went down one road. Found an insoluble flaw and had to backtrack.

This is why I like to be a simple C programmer. No need to figure out really complicated whitepapers, just the simplest solution that does the job.

[flowjob]

Hello everybody.

thought i mention my own proposal for the notary nodes election: https://github.com/KomodoPlatform/NotaryNodes/tree/master/proposals/cipi

I'm part of the KMD team and my name in slack is @cipi (it was already in use here on bitcointalk). I am with KMD from the very beginning (since the swap from BTCD), currently running 2 marketmaker nodes for BarterDEX and 6 electrum servers on AWS. If i am elected i will reinvest part of the income into upgrading this electrum servers. I plan to upgrade to larger instances (mainly because of the memory) and also to set up more of them. Since I've configured them so that you get connected to the one with the least latency, this will help make it a bit faster for the user. For the ones that want to know the details, this is the list of the electrum servers that are up and running: https://github.com/KomodoPlatform/BarterDEX/blob/dev/gui/js/electrum_list.js. The ones for BTC, GRS, HODLC, QTUM, OOT and SNG are not "mine", all others are.

Some additional words about me: I am a UNIX sysadmin with more than 20 years of experience and i worked for 3 employers:
- a server hoster (the usual data center operations)
- a company providing software and hardware for air traffic control. There i cared for the servers of some national ATCs (eg. DFS) and also some airports (eg. Singapur and Abu Dhabi)
- the last job i had was taking care of the servers of a german public TV station

I recently quit my last job in order to concentrate 100% on Komodo, BarterDEX and the Notary nodes. You could say that I am a bit dependent on having at least one node so I do not have to starve :-)

[john1962]

I do not expect much from this project
It's an excellent scam team
Just as they left a project BitcoinDark (BTCD)
Will leave this project also .... Every investor to study the matter well
It's an unsafe project
The staff list contains fake names and fake photos
Make sure it's up to you
I challenge anyone here who can prove to us the fact of having a crew in fact.

[peddycb]

john1962 I think weird that from your side only garbage comes... ( Jr. Member )

well everyone can be part of yes think which is central and decentralized

and this chit coin ( SAFE ) has shown that he is not 

[polycryptoblog]

I do not expect much from this project
It's an excellent scam team
Just as they left a project BitcoinDark (BTCD)
Will leave this project also .... Every investor to study the matter well
It's an unsafe project
The staff list contains fake names and fake photos
Make sure it's up to you
I challenge anyone here who can prove to us the fact of having a crew in fact.

Bitcoindark was swapped for Komodo and people had over a year to do so.  Komodo is Bitcoindark's evolution.

Many of the team members , myself included are public.   Some are not, and that is ok with us.

Go Troll elsewhere

[Decker]

I like one quote: "Never argue with fools, they will lower you to their level and win in their territory" ... everyone decides himself to whom apply it here.

Komodo - is one of the safest and dynamically developing projects currently. Arguments not needed, everyone who has ever used BarterDEX, kept KMD and assetchains, created his own blockchain on KomodoPlatform can confirm this.

[ComputerGenie]

I do not expect much from this project
....

As someone once said:

Intolerance of ideas is not a healthy phenomenon for anyone...

[Pumuckel21]

john1962 I think weird that from your side only garbage comes... ( Jr. Member )

well everyone can be part of yes think which is central and decentralized

and this chit coin ( SAFE ) has shown that he is not 

Yeah this is his opinion so yeah let him him have his own 'special' thoughts and hodl your token. If he decides to change his mind and join community its no problem

[jl777B]

rebased to zcash 0.15 today. its in dev branch and has all the latest zcash improvements, along with MoM support

Thanks to the zcash team for all their hard work:

Code:

str4d and others added some commits on Dec 14, 2017
 @str4d
Add Sprout value pool to getblock and getblockchaininfo
Verified
e319633
 @str4d
Apply -fstack-protector-all to libsnark
Verified
d66bf19
 @syd0
@str4d
Fix libsnark test failure.  …
Verified
4a61747
 @str4d
Add Rust and Proton to configure options printout
Verified
0100c79
 @zkbot
Auto merge of #2786 - str4d:2074-build, r=str4d  …
83af270
 @zkbot
Auto merge of #2800 - str4d:2788-libsnark-test-hardening, r=str4d …
b9c7d84
 @arcalinea
Add rpc test that exercises z_importkey
73b220c
 @zkbot
Auto merge of #2790 - bitcartel:2746_payment_disclosure_prefix, r=str4d  …
f44a4ce
 @str4d
Clarify operator precedence in serialization of nSproutValue
Verified
9d0c70e
 @zkbot
Auto merge of #2700 - kozyilmaz:emptyspaces, r=str4d  …
c720d15
 @zkbot
Auto merge of #2780 - str4d:1272-secp256k1, r=daira  …
2a48fa6
 @str4d
Remove nSproutValue TODO from CDiskBlockIndex  …
Verified
e365ca1
 @zkbot
Auto merge of #2795 - str4d:2351-sprout-circuit-value, r=str4d  …
7888624
 @per-gron
Deduplicate test utility method wait_and_assert_operationid_status …
8993edf
 @per-gron
Print result of RPC call in test only when PYTHON_DEBUG is set
d4ab94a
 @syd0
Fix libsnark dependency build.  …
a55c186
 @zkbot
Auto merge of #2796 - per-gron:less-verbose-tests, r=daira  …
efda4ba
 @zkbot
Auto merge of #2779 - arcalinea:2515_test_zimportkey, r=str4d  …
c1b0db7
 @str4d
Add Base58 encoding of viewing keys
Verified
49cf707
 @str4d
Implement viewing key storage in the wallet
Verified
167cd33
 @str4d
Add RPC methods for exporting/importing viewing keys
Verified
e85b33a
 @str4d
Update wallet logic to account for viewing keys  …
Verified
9a2b8ae
 @str4d
Add watch-only support to Zcash RPC methods  …
Verified
44e3765
 @str4d
Modify zcrawkeygen RPC method to set "zcviewingkey" to the viewing key  …
Verified
7b8d4f8
 @str4d
Cleanup: Add braces for clarity
Verified
bec2235
 @str4d
Add cautions to z_getbalance and z_gettotalbalance help text about vi…  …
Verified
2bbfe6c
 @str4d
Scope the ECDSA constant sizes to CPubKey / CKey classes
Verified
c4c7c66
 @str4d
Add release notes for incoming viewing keys
Verified
5221220
 @zkbot
Auto merge of #2143 - str4d:1997-viewing-keys, r=str4d  …
1683c2d
 @str4d
Create release notes starting from the previous non-beta non-RC release
Verified
2b38d11
 @str4d
release-notes.py: Remove unnecessary parameter
Verified
d436db6
 @str4d
Regenerate previous release notes to conform to new format  …
Verified
fd08c50
 @str4d
Exclude beta and RC release notes from author tallies  …
Verified
5d8ab77
 @zkbot
Auto merge of #2823 - str4d:2755-release-notes, r=str4d  …
7dc1e1c
 @kozyilmaz
Fix test/gtest bugs caught by latest macOS clang
bf69507
 @str4d
Fix pyflakes warnings in zkey_import_export RPC test
Verified
5d9cf8a
 @zkbot
Auto merge of #2826 - str4d:pyflakes-warnings, r=str4d  …
12cf9f1
 @str4d
make-release.py: Versioning changes for 1.0.14-rc1.
Verified
275f21a
 @str4d
make-release.py: Updated manpages for 1.0.14-rc1.
Verified
f059d52
 @str4d
make-release.py: Updated release notes and changelog for 1.0.14-rc1.
Verified
ea6ec71
str4d and others added some commits on Dec 22, 2017
 @str4d
Update release process
Verified
5cbf238
 @zkbot
Auto merge of #2830 - str4d:release-v1.0.14-rc1, r=str4d  …
8912a06
 @str4d
Enable Bash completion for -exportdir
Verified
2941e07
 @arcalinea
Add getdeprecationinfo rpc call to return current version and depreca…  …
9d2974e
 @str4d
Check chainValueZat when checking value pool monitoring
Verified
44e5b42
 @str4d
make-release.py: Versioning changes for 1.0.14.
Verified
2091cf2
 @str4d
make-release.py: Updated manpages for 1.0.14.
Verified
d3c1949
 @str4d
make-release.py: Updated release notes and changelog for 1.0.14.
Verified
6bfa0fb
 @zkbot
Auto merge of #2849 - str4d:release-v1.0.14, r=str4d  …
1ddecf6
 @zkbot
Auto merge of #2821 - str4d:2335-scope-ecdsa-constants, r=str4d  …
db9f6f0
 @syd0
@str4d
Remove OSX and Windows files from Makefile + share directory.  …
Verified
b6a990d
 @zkbot
Auto merge of #2770 - syd0:remove-some-cruft, r=str4d  …
8dbe114
 @zkbot
Auto merge of #2771 - syd0:fix-snark-dep-build, r=str4d  …
b2a114a
 @sandakersmann
Changed http:// to https:// on some links  …
Verified
a3e09f2
 @zkbot
Auto merge of #2858 - sandakersmann:patch-1, r=daira  …
0ad9255
 @bitcartel
Fixes #2793. Backport commit f33afd3 to increase dbcache default.
5befbed
 @zkbot
Auto merge of #2845 - str4d:exportdir-completion, r=str4d  …
d80ab8a
 @zkbot
Auto merge of #2848 - str4d:2795-rpc-test-chainValueZat, r=str4d …
fdb5926
 @bitcartel
Add documentation about dbcache.  …
334d591
 @bitcartel
Add note about dbcache to 1.0.15 release notes.  …
d2b77b7
 @zkbot
Auto merge of #2873 - bitcartel:2793_dbcache, r=bitcartel  …
38246ea
 @bitcartel
Remove redundant service flag NODE_GETUTXO meant for Bitcoin XT. …
03a61ed
 @maaku
@str4d
Explicitly set tx.nVersion for the genesis block and mining tests …
Verified
fe53749
 @theuni
@str4d
chainparams: move CCheckpointData into chainparams.h  …
Verified
47b71ce
 @theuni
@str4d
chainparams: don't use std namespace
Verified
91690d6
 @jtimon
@str4d
Chainparams: Introduce CreateGenesisBlock() static function
Verified
90b6ee6
 @jtimon
@str4d
Chainparams: CTestNetParams and CRegTestParams extend directly from C…  …
Verified
54ab3b3
 @domob1812
@str4d
Clean up chainparams some more.  …
Verified
a97308c
 @str4d
Add missing namespace for boost::get
Verified
ff145df
 @str4d
Add viewing key prefix to regtest parameters
Verified
40ebf08
 @zkbot
Auto merge of #2886 - bitcartel:2885_cleanup_node_getutxo, r=str4d …
d11230b
 @str4d
zkey_import_export: Synchronize mempools before mining  …
Verified
9e8f1d0
 @zkbot
Auto merge of #2897 - str4d:2892-zkey-rpc-bugfix, r=str4d  …
b4a20ae
 @zkbot
Auto merge of #2217 - str4d:2074-chainparams, r=str4d  …
a4a020d
 @JohnDolittle
@bitcartel
remove unused NOBLKS_VERSION_{START,END} constants
20bfa35
 @zkbot
Auto merge of #2902 - bitcartel:2901_remove_unused_noblks_constants, …  …
70109a7
 @arcalinea
Make applicable only on mainnet
df46562
 @str4d
Use JoinSplitTestingSetup for Boost sighash tests  …
Verified
35d64c1
 @zkbot
Auto merge of #2839 - arcalinea:add_deprecation_alert, r=bitcartel …
a0a010c
 @str4d
Network upgrade activation mechanism
Verified
780f526
 @str4d
Allow changing network upgrade parameters on regtest  …
Verified
b174b7e
 @str4d
Test network upgrade logic  …
Verified
f52da91
 @sipa
@str4d
Add rewind logic to deal with post-fork software updates  …
Verified
89f2045
 @str4d
Adjust rewind logic to use the network upgrade mechanism
Verified
9e85145
 @str4d
Add Overwinter to upgrade list
Verified
5486837
 @str4d
Add method for fetching the next activation height after a given bloc…  …
Verified
149d69e
 jc
read hashReserved from disk block index
Unverified
15fb13f
 @str4d
Use a boost::optional for nCachedBranchId  …
Verified
828940b
 @str4d
Change UI/log status message for block rewinding
Verified
5009136
 @str4d
Update quote from ZIP 200
Verified
cad27eb
 @zkbot
Auto merge of #2898 - str4d:2286-nu-activation-mechanism, r=str4d …
e685057
 @ashleyholman
@str4d
TxMemPool: Change mapTx to a boost::multi_index_container  …
Verified
e328fa3
 @sipa
@str4d
Support -checkmempool=N, which runs checks on average once every N tr…  …
Verified
934fd19
 @morcos
@str4d
Implement helper class for CTxMemPoolEntry constructor  …
Verified
f41775b
 @zkbot
Auto merge of #2923 - str4d:sighash-tests-env-bug, r=str4d  …
d527116
 @bitcartel
Implementation of Overwinter transaction format ZIP 202.
072099d
 @str4d
@bitcartel
Update SignatureHash tests for transaction format changes  …
46d3762
 @zkbot
Auto merge of #2925 - bitcartel:2906_overwinter_tx_format, r=str4d …
c6ffabb
 @bitcartel
Add test to check malformed v1 transaction against Overwinter tx parser
fa78211
 @zkbot
Auto merge of #2958 - bitcartel:2906_extra_test, r=str4d  …
8da60b1
 @str4d
Implement roll-back limit for reorganisation  …
Verified
57e6ecd
 @str4d
Add rollback limit to block index rewinding  …
Verified
cb580c7
 @rofl0r
fix build error due to usage of obsolete boost_system-mt  …
Verified
36d8b2e
 @TheBlueMatt
@str4d
Add failing test checking timelocked-txn removal during reorg
Verified
b0f8c83
 @TheBlueMatt
@str4d
Fix removal of time-locked transactions during reorg
Verified
f5b35d2
 @TheBlueMatt
@str4d
Fix comment in removeForReorg
Verified
c944d16
 @TheBlueMatt
@str4d
Make indentation in ActivateBestChainStep readable
Verified
5aa165d
 @TheBlueMatt
@str4d
removeForReorg calls once-per-disconnect-> once-per-reorg
Verified
fe5cef0
 @sdaftuar
@str4d
Track coinbase spends in CTxMemPoolEntry  …
Verified
a4b2518
 @sdaftuar
@str4d
Don't call removeForReorg if DisconnectTip fails
Verified
e52ba51
 @sdaftuar
@str4d
Fix removeForReorg to use MedianTimePast
Verified
233c9eb
 @str4d
Remove mempool transactions which commit to an unmineable branch ID
Verified
34a64fe
 @zkbot
Auto merge of #2940 - str4d:nu-activation-mempool-expiry, r=str4d …
4927455
 @sipa
@str4d
Report non-mandatory script failures correctly
Verified
838e7a2
 @21E14
@str4d
Remove obsolete reference to CValidationState from UpdateCoins.
Verified
8cb98d9
 @jonasnick
@str4d
Reduce unnecessary hashing in signrawtransaction
Verified
ffda7e0
 @sipa
@str4d
Refactor script validation to observe amounts  …
Verified
2d42e1a
 @sipa
@str4d
BIP143: Signing logic
Verified
157a5d0
 @sipa
@str4d
BIP143: Verification logic  …
Verified
c86a1cb
 @str4d
Remove P2WPKH and P2WSH from signing logic  …
Verified
e005ff8
jtimon and others added some commits on Jul 16, 2016
 @jtimon
@str4d
Mempool: Use Consensus::CheckTxInputs direclty over main::CheckInputs
Verified
722d811
 @NicolasDorier
@str4d
Unit test for sighash caching  …
Verified
90285e7
 @sipa
@str4d
Rename to PrecomputedTransactionData
Verified
6514771
 @sipa
@str4d
Precompute sighashes  …
Verified
f762d44
 @str4d
Add consensus branch ID parameter to SignatureHash, remove SigVersion…  …
Verified
be12669
 @arielgabizon
@str4d
add blake2b writer
Verified
132dc81
 @arielgabizon
@str4d
update SignatureHash according to Overwinter spec  …
Verified
7245f32
 @str4d
Regenerate SignatureHash tests
Verified
a3353b4
 @str4d
Cleanup: Wrap function arguments
Verified
d55e5e7
 @str4d
Use v3 transactions with caching for validatelargetx benchmark
Verified
4553901
 @str4d
Make number of inputs configurable in validatelargetx test
Verified
818b94f
 @zkbot
Auto merge of #2903 - str4d:1408-sighash, r=str4d  …
8487be8
 @str4d
Extend CWallet::GetFilteredNotes to enable filtering on a set of addr…  …
Verified
bdbe8e8
 @maxgubler
Fix syntax examples for z_importwallet and export
f70cd24
 @zkbot
Auto merge of #2463 - str4d:713-rollback-limit, r=str4d  …
d4d2844
 @arcalinea
@str4d
Add upgrades field to RPC call getblockchaininfo  …
Verified
7176855
 @str4d
Add branch IDs for current and next block to getblockchaininfo  …
Verified
ed9aa2b
 @zkbot
Auto merge of #2931 - jc23424:hashreserved-diskindex, r=str4d  …
6264927
 @str4d
Check Equihash solution when loading block index
Verified
4448840
 @zkbot
Auto merge of #2977 - str4d:loadblockindexguts-correctness, r=str4d …
5040031
 @zkbot
Auto merge of #2968 - maxgubler:v1.0.14-edit, r=str4d  …
933e0d6
 @str4d
Implement z_mergetoaddress for combining UTXOs and notes  …
Verified
6e9c762
 @str4d
Gate z_mergetoaddress as an experimental feature
Verified
553a5c1
 @str4d
Add z_mergetoaddress to release notes
Verified
2bda6a9
 @str4d
Check upgrade status in wallet_overwintertx RPC test
Verified
4c3d2b3
 @str4d
Document that consensus.chaintip != consensus.nextblock just before a…  …
Verified
50a9061
 @zkbot
Auto merge of #2808 - arcalinea:2785_upgrades_rpc, r=str4d  …
c2d98b4
 @bitcartel
@str4d
Closes #2964. z_sendmany once again makes v1 tx for taddr to taddr. …
Verified
e6cd2a8
 @zkbot
Auto merge of #2978 - bitcartel:2906_v1_tx_no_assert, r=str4d  …
0be6cb9
 @bitcartel
@str4d
Closes #2954 and #2959. Fixes Overwinter issues in sighash_tests.
Verified
07f9435
 @str4d
Regenerate sighash tests
Verified
713b366
 @zkbot
Auto merge of #2960 - bitcartel:2959_overwinter_fix_sighash_test, r=s…  …
f472edd
 @str4d
wallet_mergetoaddress: Add additional syncs to prevent race conditions
Verified
15ced9b
 @zkbot
Auto merge of #2797 - str4d:2493-active-merging, r=bitcartel  …
c5904fb
 @arcalinea
Implement transaction expiry for Overwinter
9bb37bf
 @arcalinea
Add -txexpirydelta cli option
9c12b8e
 @arcalinea
Add mempool_tx_expiry.py test
5943f22
 @rofl0r
remove -mt suffix from boost libraries built by depends
33ae5ed
 @bitcartel
Add field nProtocolVersion to struct NetworkUpgrade.
2423a40
 @bitcartel
Overwinter peer management and network handshaking.  …
72b2192
 @bitcartel
Add python qa test overwinter_peer_management.
b6e5cc7
 @arcalinea
Add expiry to z_mergetoaddress
7b92f27
 @zkbot
Auto merge of #2919 - bitcartel:2904_branch_id_protocol_handshake, r=…  …
e6e483b
 @arcalinea
Change rpc_tests to 21
59da58c
 @zkbot
Auto merge of #2874 - arcalinea:tx_block_expiry, r=arcalinea  …
a418756
 @str4d
make-release.py: Versioning changes for 1.0.15-rc1.
Verified
1dd95be
 @str4d
make-release.py: Updated manpages for 1.0.15-rc1.
Verified
7d0c1df
 @str4d
make-release.py: Updated release notes and changelog for 1.0.15-rc1.
Verified
34ce29b
 @zkbot
Auto merge of #2985 - str4d:release-v1.0.15-rc1, r=ebfull  …
be262f0
 @leto
Fix references to Bitcoin in RPC tests readme
427e5fa
 @str4d
@braddmiller
Use block hash comparison for consistency check when loading block index  …
Verified
704b763
 @zkbot
Auto merge of #2993 - str4d:2977-performance-regression, r=str4d …
f9dbd1e
 @str4d
Overwinter release notes and testnet activation height  …
Verified
138cf77
 @zkbot
Auto merge of #3002 - str4d:2957-overwinter-release-notes, r=str4d …
b10aaac
 @str4d
make-release.py: Versioning changes for 1.0.15.
Verified
1d6f7ac
 @str4d
make-release.py: Updated manpages for 1.0.15.
Verified
f58b153
 @str4d
make-release.py: Updated release notes and changelog for 1.0.15.
Verified
25b080a
 @zkbot
Auto merge of #3030 - str4d:release-v1.0.15, r=str4d  …
93332d6
 @leto
This library seems to not be used at all and all comments mentioning …  …
d8399ef
 @leto
Update awkward wording about blocks as per @daira
62fee12
 @leto
Regtest mining does have a founders reward, a single address t2FwcEhF…  …
48cecf2
 @leto
Fix outdated comment about starting balance of nodes
4db8717
 @str4d
Add environment variable for setting ./configure flags in zcutil/buil…  …
Verified
326fc65
 @str4d
@rcseacord
Add configure flags for enabling ASan/UBSan and TSan  …
Verified
c4379e3
 @jasondavies
Fix typo in comment: should link to issue #1359.
4ec29af
 @daira
Squashed commit of the following:  …
c938fb1
 @zkbot
Auto merge of #3027 - rex4539:master, r=daira  …
112ec98
 @zkbot
Auto merge of #3036 - plutomonkey:typo, r=daira  …
9a6a81a
 @zkbot
Auto merge of #2965 - rofl0r:patch-1, r=str4d  …
796ea38
 @bitcartel
Code clean up. Remove use of X macro.
7e9d662
 @zkbot
Auto merge of #2987 - leto:rpc-readme, r=bitcartel  …
99d9e14
 @zkbot
Auto merge of #3048 - str4d:analysis-tools, r=str4d  …
b3a656c
 @braddmiller
Clean up
e882e3c
 @zkbot
Auto merge of #3050 - bitcartel:cleanup_define_X, r=daira  …
d88a122
 @str4d
Split declaration and definition of SPROUT_BRANCH_ID constant  …
Verified
a6ae8f5
 @daira
pyflakes cleanups to RPC tests after Overwinter PRs.  …
b4353db
 @str4d
Add link to Overwinter info page
Verified
132a255
 @zkbot
Auto merge of #3079 - daira:pyflakes-cleanup, r=str4d  …
5abe4e6
 @zkbot
Auto merge of #3089 - kozyilmaz:clang, r=str4d  …
bc8221d
 @zkbot
@mdr0id
Auto merge of #3069 - braddmiller:3034-disable-auto-dep, r=daira …
01c31ec
bitcartel and others added some commits 9 days ago
 @bitcartel
Enable mempool logging in tx expiry QA test.
a510b47
 @bitcartel
Closes #3084. Log txid when removing expired txs from mempool.
eb13862
 @bitcartel
Add qa test for cache invalidation bug found in v1.0.0 to v1.0.3.
2f76137
 @bitcartel
Remove local function wait_and_assert_operationid_status which is …
b740a99
 @zkbot
Auto merge of #3093 - bitcartel:3092_clean_up_qa_test_operationid_sta…  …
601fc24
 @zkbot
Auto merge of #3090 - bitcartel:3084_log_expired_txid, r=bitcartel …
70e2522
 @zkbot
Auto merge of #3091 - bitcartel:cache_invalidation_qa, r=str4d  …
64de921
 @zkbot
Auto merge of #3077 - str4d:asan-initialization-order-fiasco, r=str4d …
8ed0346
 @zkbot
Auto merge of #3082 - str4d:overwinter-info, r=daira  …
4d6498b
 @jl777
Merge remote-tracking branch 'zcash/master' into rebase2  …
9000990

All of the KMD specific improvements are outside the zksnark tech, we rely on zcash's cutting edge zksnark tech improvements for the privacy tech of KMD.

[GröBkAz]

We installed Barterdex the very first time and i also must state you men did a great job. You can easily use and also the structure is extremely user friendly for your early advancement stage.