Live data from Hacker News

Show HN: Interactive implementation of the NIST Blockchain use case flow chart

brucemacd.github.io

1–10 of 30 posts

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#2
I think there's a bug in this. If I answer "Will data records ever need to be updated or deleted once they are written?" with "No" it says "You Don't Need a Blockchain Blockchains do not allow for modification of historical data. Consider a database." It seems like blockchains actually meet that requirement per my entry?

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#3
post #2

I think there's a bug in this. If I answer "Will data records ever need to be updated or deleted once they are written?" with "No" it says "You Don't Need a Blockchain Blockchains do not allow for modification of historical data. Consider a database." It seems like blockchains actually meet that requirement per my entry?

Yep I hit the same bug, if you answer “yes” the next question has the same bug.

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#4
post #2

I think there's a bug in this. If I answer "Will data records ever need to be updated or deleted once they are written?" with "No" it says "You Don't Need a Blockchain Blockchains do not allow for modification of historical data. Consider a database." It seems like blockchains actually meet that requirement per my entry?

Just fixed the wording to match the actual NIST flowchart. Thanks.

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#5
>Data records, once written, are never updated or deleted?

>Blockchains do not allow for modification of historical data. Consider a database.

If that was true it wouldn't even be possible to send any tokens. Log of all past actions can't be deleted or updated, which is a quite different thing.

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#8
post #7

This toy is BS. Please include a justification for the decision. What do you think you are? The mysterious oracle telling earthly idiots what they need? How arrogant!

Don't take it too seriously. I was trying for a similar vibe to "howfuckedismydatabase.com".

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#9
post #7

This toy is BS. Please include a justification for the decision. What do you think you are? The mysterious oracle telling earthly idiots what they need? How arrogant!

Don't take it too seriously. I was trying for a similar vibe to "howfuckedismydatabase.com".

No worries about being taken seriously.

Re: Show HN: Interactive implementation of the NIST Blockchain use case flow chart

#10

>Data records, once written, are never updated or deleted? >Blockchains do not allow for modification of historical data. Consider a database. If that was true it wouldn't even be possible to send any tokens. Log of all past actions can't be deleted or updated, which is a quite different thing.

The log entries in a blockchain are supposed to be immutable. You can add new entries, but not change old ones.
Post reply on HN