Topic: source code reading (Read 579 times)
any new ideas about this?
Quis custodiet ipsos custodes?
Etiam. Admodum.
Quod est magni momenti quaestionem.
Hoc est quod intelligitur, cum dicitur:
"Num merentur scripta legentes lucrentur famam, a frenum sicut escrows?"
https://www.google.de/search?q=code+comparison+tools code comparison tools
https://www.google.de/search?q=diff diff
https://www.google.de/search?q=windiff windiff
Is there a way to always know from which code a new coin has been forked?
Then it needs "only" incremental comparisons from that codebase.
https://www.google.de/search?q=diff diff
https://www.google.de/search?q=windiff windiff
Is there a way to always know from which code a new coin has been forked?
Then it needs "only" incremental comparisons from that codebase.
400k lines of code...thanks for the info
A quick count shows about 400,000+ lines of code in Bitcoin 0.9.1!
Checking a code base like this is a highly nontrivial task.
400k lines of code is not much. Code auditing is not done by hand anymore, except in rare occasions (like FreeBSD audit) Checking a code base like this is a highly nontrivial task.
A quick count shows about 400,000+ lines of code in Bitcoin 0.9.1!
Checking a code base like this is a highly nontrivial task.
git ls-files | xargs wc -l
1 .gitattributes
84 .gitignore
19 COPYING
4 INSTALL
160 Makefile.am
71 README.md
5 autogen.sh
****
594 src/util.h
66 src/version.cpp
51 src/version.h
2075 src/wallet.cpp
865 src/wallet.h
963 src/walletdb.cpp
133 src/walletdb.h
418370 total
Checking a code base like this is a highly nontrivial task.
git ls-files | xargs wc -l
1 .gitattributes
84 .gitignore
19 COPYING
4 INSTALL
160 Makefile.am
71 README.md
5 autogen.sh
****
594 src/util.h
66 src/version.cpp
51 src/version.h
2075 src/wallet.cpp
865 src/wallet.h
963 src/walletdb.cpp
133 src/walletdb.h
418370 total
Quis custodiet ipsos custodes?
Ya need experienced programmer to validate these coins before someone else gets taken to cleaners
This is a much needed thing, I'm glad someone is trying to incentivize and reward it. It would certainly stop people from creating malware wallets like we've seen...
... there are already bounties for block explorers, for games, for faucets, for pools, ...
What about (crowd)bounties to have the source code of a new coin thoroughly checked!!
How to operationalize that? Let's brainstorm.
Especially pools, and exchanges could finance a "certified ... stamp"
to show that some effort has been put into proof reading the sourcecode,
from an independent side.
How could reliable code readers earn reputation, a bit like escrows?
What are your thoughts on this ... thx!
What about (crowd)bounties to have the source code of a new coin thoroughly checked!!
How to operationalize that? Let's brainstorm.
Especially pools, and exchanges could finance a "certified ... stamp"
to show that some effort has been put into proof reading the sourcecode,
from an independent side.
How could reliable code readers earn reputation, a bit like escrows?
What are your thoughts on this ... thx!
---
Me need: pay me if you want me to continue to afford to spend time
and share ideas here: 17v4HC9bW5MTagCUAgCn977LAD4xc8RQPU
Me need: pay me if you want me to continue to afford to spend time
and share ideas here: 17v4HC9bW5MTagCUAgCn977LAD4xc8RQPU
Jump to: