Coder Social home page Coder Social logo

simpleblockchain's People

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

saadmahboob shardayyyy tagger1986 davidbongcc micadrlam moanouti kyo88 yotamhassin gedzakis abhishek021 seanfmcdonnell haniq8 devcryptoph mohitsharma1750 pokekarat woonyung89 wajayanath paulblartcoin fishsticks123 lingnet adel-ewis adamdxc archoncap rohit3594 biplob45 rs19hack cinvoke schr588 livindelife prasadeej marcelogra jiuzhuyou aidangillespie macsketeer kundan15692 goldmoke isonomic jimmylegget alfo1002 aliphucphuc17 tgroh007 tycooperaow yancongli sharonfirebase saadbilal rubynguyen-infocorp rohitooo neritrading akbaloch ry4bb theantisnipe radling msgpo ttilling tukantisiva seif-abaza juanmagmen leanderdulac skanel andrewbert alexsvetlov programmermail pardus-md pranavdaa code-abil pretzelpanda13 johnwati garant07

simpleblockchain's Issues

Maybe point out in the code (comments) to never actually use hashCode() but use a (strong) cryptographic hash function?

I liked your video but one important thing, to me, that was missing was that you never once pointed out that hashCode() is a horrible choice. It's nice for a quick and simple demonstration but you should've pointed out (IMHO) that hashCode is never, ever, ever to be used but an actual cryptographic hash like SHA-256 (and even only a subsection of those since MD5 for example is, for all intents and purposes, broken). Every hash has, by definition, collisions but collisions in cryptographic hashes are very hard to create (making it hard to falsify transactions) but hashCode() is, and was, never intended to be used for such purposes and is very easy to "fool" (e.g. find some creative way to 'pad' the transactions with some whitespace here-and-there for example to result in the same hashcode).

I'm not sure you are aware of this (I'm assuming you are) but if not I'm glad to explain a bit more in-depth.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.