BlockChan - Censorship Resistant Message Board

[Hyena]

This is a quick side-project of mine, mainly developed as a template/example for other developers who want to save custom messages on the block chain. The base functionality is derived from CryptoGraffiti.info.

Source code: https://github.com/1Hyena/blockchan

Possible use cases include censorship resistant commenting under any keyword. For example, let's say you have a blog but you want to enable censorship resistant commenting for your site. Then you would simply include BlockChan in an IFRAME sandbox below your blog with the following source: http://cryptograffiti.info/chan#myblog.com/blogpost123
The iframe will display all the messages written under the "myblog.com/blogpost123" category (case sensitive).

I will gladly explain the technical details when asked. Just let me know if you have any questions.

Here are some screenshots:

[1714839253]

1714839253

[1714839253]

1714839253

[1714839253]

1714839253

[1714839253]

1714839253

[1714839253]

1714839253

[1714839253]

1714839253

[Kprawn]

I am curious to know how this validates messages using the Blockchain? Would you have to make a tx every time you make a entry on this

message board?  I am looking for a easy method to include messages for the general public onto the Blockchain and something that would

validate that those messages cannot be erased or tampered with. Good work. 

[Hyena]

I am curious to know how this validates messages using the Blockchain? Would you have to make a tx every time you make a entry on this

message board?  I am looking for a easy method to include messages for the general public onto the Blockchain and something that would

validate that those messages cannot be erased or tampered with. Good work. 

1 message = 1 new bitcoin transaction

the number of confirmations for the respective transaction is all the validation that you need

[PremiumCodeX]

Inspiring, it is. Thank you for contributing Us! This project could be a neat component of any blog. My question: Is it a good practice to combine components that use different blockchains in the same project? Or should I stick with components using the same blockchain?

[Hyena]

Inspiring, it is. Thank you for contributing Us! This project could be a neat component of any blog. My question: Is it a good practice to combine components that use different blockchains in the same project? Or should I stick with components using the same blockchain?

from the end user's perspective it doesn't matter very much. but the implementation will be way more complex if you wanted to support multiple block chains

[0xfff]

It's not really a "chan" if the posts last forever on the blockchain.

[Hyena]

It's not really a "chan" if the posts last forever on the blockchain.

Why not? it is a channel of one-way communication much like radio channels are. except here erryone can broadcast their messages in any channel they wish

[0xfff]

Also I dont get how this is censorship resistant if it relies on 1 central server. Just beacause it is on "muh blockchain" doesnt make it censorphip resistant.

[Hyena]

Also I dont get how this is censorship resistant if it relies on 1 central server. Just beacause it is on "muh blockchain" doesnt make it censorphip resistant.

what 1 server are you referring to? You don't seem to know what you're talking about. The messages are stored in all bitcoin full nodes because they are part of the block chain. you can take the source code I linked in the OP and run the software on your computer if you want. you can check out https://bitcoinstrings.com/ if you want to view the messages in some other server.

[rajasumi3]

Thanks a lot for this project and i look forward to it .but i have one question . Will the messages during the communication is totally secured?

[Hyena]

Thanks a lot for this project and i look forward to it .but i have one question . Will the messages during the communication is totally secured?

message integrity is protected by the most powerful computing network on Earth. message confidentiality is up to the users but all messages are public by default.

[Emerge]

Pretty cool!
Thanks for open sourcing it, will really help the community!

[PremiumCodeX]

from the end user's perspective it doesn't matter very much. but the implementation will be way more complex if you wanted to support multiple block chains

Thank you for reply! Logical. It throws the question, though: Would we need a "blockchain management" software that helps manage multiple blockchain in the same project? I am visualising a software such as "version management software" and I want to point out how it became part of our professional development environment. Could a "blockchain management software" be the next element in our toolbox?

[Hyena]

from the end user's perspective it doesn't matter very much. but the implementation will be way more complex if you wanted to support multiple block chains

Thank you for reply! Logical. It throws the question, though: Would we need a "blockchain management" software that helps manage multiple blockchain in the same project? I am visualising a software such as "version management software" and I want to point out how it became part of our professional development environment. Could a "blockchain management software" be the next element in our toolbox?

Well it could turn useful but we'd need a practical example first. If you can't come up with a problem where a block chain management software is the solution then it is probably not a viable idea. Also, ever since ByteBall was launched the block chain tech is no longer the coolest thing out there. Turns out that now we don't even need a block chain for consensus tracking. ByteBall is the first cryptocurrency that does not depend on a block chain and thus does not need to be mined and does not have an issue of blocks getting full. For that reason I wouldn't invest into block chain tech any more. It is already becoming obsolete

[Kprawn]

I am curious to know how this validates messages using the Blockchain? Would you have to make a tx every time you make a entry on this

message board?  I am looking for a easy method to include messages for the general public onto the Blockchain and something that would

validate that those messages cannot be erased or tampered with. Good work. 

1 message = 1 new bitcoin transaction

the number of confirmations for the respective transaction is all the validation that you need

Ok, the concept is good .. but this will spam the Blockchain with tx's and we cannot handle loads of tx's that are not related to financial purposes.

I think SatoshiDice or one of these gambling sites, did the same back in the day and everyone complained about that. Why put the Blockchain

under unnecessary strain? { How would this work with LN? ... because you need this to be linked directly with the Blockchain. } 

[Hyena]

Ok, the concept is good .. but this will spam the Blockchain with tx's and we cannot handle loads of tx's that are not related to financial purposes.

I think SatoshiDice or one of these gambling sites, did the same back in the day and everyone complained about that. Why put the Blockchain

under unnecessary strain? { How would this work with LN? ... because you need this to be linked directly with the Blockchain. } 

bitcoin devs would have to find a way how to make the network handle an ever-increasing number of UTXOs. If this really is a threat to Bitcoin then the adversaries of Bitcoin would be doing this for long time already. So no worries here.

Lightning network has nothing to do with it. TXs made in the LN won't be saved on the block chain. Lightning network is bullshit anyway because lightning is a code word for banking. It's the banking network that they want to turn Bitcoin into. So that eventually only banks would be able to make bitcoin transactions and therefore have absolute control over Bitcoin. The block size should be increased so that Bitcoin would scale on-chain. Payment channels are a good idea and should be properly implemented as part of the Bitcoin protocol not in an ugly hack known as SegWit. I'd suggest everyone to reject SegWit, stop using bitcoin-core and instead switch to either Bitcoin Classic or Bitcoin Unlimited.