Topic: Bubble is coming... are you ready? (Read 530 times)
Invalid Invite Links
discord invite link died
Overview of the Proposed Blockchain System
Key Components
Multi-Signature Scheme:
The blockchain system utilizes a Boneh-Lynn-Shacham (BLS) multi-signature scheme, enhancing security and mitigating replay attacks by linking each transaction to previous signatures.
Efficient Data Encoding:
Huffman Coding is employed for transaction data, allowing for compact representation and improved processing efficiency without compromising integrity.
Parsing Huffman Data:
Upon receipt, transactions encoded using Huffman coding are parsed in their raw format. This parsing process involves decoding the Huffman-encoded data back into its original form, enabling the verification of the transaction's authenticity.
Parsing is crucial for validating the integrity of each transaction before it is added to the blockchain, ensuring that any malicious alterations can be detected before they compromise the network.
Time-Based Mining Mechanism:
The system enforces a time-based mining scheme that ensures fairness by regulating the mining process to a specific time interval. This restriction prevents a single miner from quickly confirming multiple blocks in succession, reinforcing the decentralization and integrity of the blockchain.
Each block is validated against an exact copy held by every participant in the network, with mining rounds being serialized. This means that the mining of new blocks depends on data from the previous block, including its hash and multi-signature.
Collective Responsibility:
Participants in the network are not just miners; they are integral to the network's efficiency. By requiring users to contribute their bandwidth for data relaying, each participant is accountable for maintaining the health and speed of the network.
Transaction Flow
Transaction Creation:
Each sender hashes their transaction data, referred to as “huff tx,” using a predefined Huffman tree generated from a shared dictionary.
The sender then signs the hash of this Huffman-compressed transaction data.
Huffman Data Parsing:
Transactions encoded with Huffman coding are parsed to decode the original transaction details. This parsing allows for validation against the network's consensus rules, ensuring that no double spending occurs.
During parsing, checksums or cryptographic hashes can be employed to ensure the integrity of the decoded data, reinforcing trust in the transactions.
Block Creation:
Miners aggregate signatures from multiple senders, including the previous block's multi-sig, to form a new aggregate signature. This ensures that all signatures are acknowledged and securely linked, reinforcing the distributed trust model.
51% Attack and Double Spend Mitigation
51% Attack:
To mitigate the risk of a 51% attack, where a single entity controls the majority of the network's mining power, the system employs a decentralized mining structure and time-based restrictions on mining success.
By encouraging participation from a diverse array of devices, including older technology, the network becomes more resilient to centralization. This diversity makes it difficult for any single entity to control a significant percentage of the mining power.
Double Spend Prevention:
Each transaction is tied to previous signatures and transaction data, creating a robust record that can be easily verified during parsing.
If a user attempts to double spend, the network's consensus mechanism will flag the conflicting transactions during the parsing stage, preventing them from being added to the blockchain.
The use of serialized mining rounds ensures that only one block is accepted at a time, with each new block dependent on the data from the previous one. This serialization significantly reduces the chances of double spending since any conflicting transactions would not be valid due to the linkage to prior blocks.
Signature Context
Each transaction ties back to the previous transaction’s signature, creating a unique context for validation. The system incorporates both the transaction hash and the previous signature in the signing process, ensuring contextual linking.
Replay Attack Mitigation
By incorporating the previous signature into every transaction, the system significantly reduces the likelihood of successful replay attacks. An attacker would have to manipulate the context of a valid transaction, which is tightly controlled.
Integrity Through Aggregation
Aggregating signatures across transactions enhances trust and ensures that all participant signatures are valid, creating a robust validation mechanism for each block.
Strengths of the System
Mitigation of Signature Ambiguity:
Hashing each transaction before signing prevents ambiguity in signature validation, ensuring clear and unique representations.
Enhanced Security Against Replay Attacks:
By tying each transaction to the previous signature, the system reduces the likelihood of replay attacks.
Chain of Trust:
The sequential linking of transactions establishes a chain of trust, reinforcing the integrity of the blockchain.
Efficient Data Representation:
Using Huffman coding improves transaction processing efficiency, enabling better performance without sacrificing security.
Distributed Trust Model:
The requirement for multiple signatures reduces reliance on any single participant, enhancing resilience against collusion and single points of failure.
Collective Network Performance:
By encouraging users to repurpose old technology (like old laptops and smartphones) for mining and data relaying, the network becomes more robust. Users' contributions to bandwidth and processing power enhance the network's speed and efficiency.
Areas of Weakness and Recommendations
Hash Function Security:
The system's security relies heavily on the hash function used. Ensure the use of robust cryptographic hash functions (e.g., SHA-256 or SHA-3) to prevent collision attacks.
Signature Aggregation Complexity:
The aggregation process must be clearly defined to avoid errors in signature validation. Implement checks and balances for validating aggregated signatures.
BLS Single Signature Context:
To avoid potential vulnerabilities, consider implementing nonce mechanisms or additional unique identifiers for each transaction.
Replay Attack Mitigation:
Additional context checks, such as timestamps or nonces, can further ensure that each transaction is validated against its intended context.
Shared Dictionary Vulnerability:
Secure management of the shared dictionary is essential. Consider using a hashing mechanism for dictionary entries to detect unauthorized modifications.
Potential for Denial of Service (DoS):
Implement rate limiting and transaction validation checks to mitigate DoS attack risks.
Complexity of Signature Verification:
Thoroughly test the signature verification process to identify potential weaknesses and ensure robustness.
Cryptographic Assumptions:
Stay informed about developments in cryptographic research and adapt to newer, more secure signature schemes if necessary.
Conclusion
The proposed blockchain system effectively integrates innovative methods to address challenges associated with BLS multi-signature schemes, transaction integrity, efficient data encoding, and robust double spending prevention. By linking transactions contextually, employing Huffman coding, and implementing a decentralized mining framework, the system establishes a resilient and secure foundation for transactions. Additionally, the collective responsibility of network participants enhances network efficiency and resilience, creating a community-oriented ecosystem.
This combination of technological innovation and social responsibility positions the system for a sustainable future, empowering participants to contribute to a faster and more secure decentralized network while benefiting from their involvement.
Key Components
Multi-Signature Scheme:
The blockchain system utilizes a Boneh-Lynn-Shacham (BLS) multi-signature scheme, enhancing security and mitigating replay attacks by linking each transaction to previous signatures.
Efficient Data Encoding:
Huffman Coding is employed for transaction data, allowing for compact representation and improved processing efficiency without compromising integrity.
Parsing Huffman Data:
Upon receipt, transactions encoded using Huffman coding are parsed in their raw format. This parsing process involves decoding the Huffman-encoded data back into its original form, enabling the verification of the transaction's authenticity.
Parsing is crucial for validating the integrity of each transaction before it is added to the blockchain, ensuring that any malicious alterations can be detected before they compromise the network.
Time-Based Mining Mechanism:
The system enforces a time-based mining scheme that ensures fairness by regulating the mining process to a specific time interval. This restriction prevents a single miner from quickly confirming multiple blocks in succession, reinforcing the decentralization and integrity of the blockchain.
Each block is validated against an exact copy held by every participant in the network, with mining rounds being serialized. This means that the mining of new blocks depends on data from the previous block, including its hash and multi-signature.
Collective Responsibility:
Participants in the network are not just miners; they are integral to the network's efficiency. By requiring users to contribute their bandwidth for data relaying, each participant is accountable for maintaining the health and speed of the network.
Transaction Flow
Transaction Creation:
Each sender hashes their transaction data, referred to as “huff tx,” using a predefined Huffman tree generated from a shared dictionary.
The sender then signs the hash of this Huffman-compressed transaction data.
Huffman Data Parsing:
Transactions encoded with Huffman coding are parsed to decode the original transaction details. This parsing allows for validation against the network's consensus rules, ensuring that no double spending occurs.
During parsing, checksums or cryptographic hashes can be employed to ensure the integrity of the decoded data, reinforcing trust in the transactions.
Block Creation:
Miners aggregate signatures from multiple senders, including the previous block's multi-sig, to form a new aggregate signature. This ensures that all signatures are acknowledged and securely linked, reinforcing the distributed trust model.
51% Attack and Double Spend Mitigation
51% Attack:
To mitigate the risk of a 51% attack, where a single entity controls the majority of the network's mining power, the system employs a decentralized mining structure and time-based restrictions on mining success.
By encouraging participation from a diverse array of devices, including older technology, the network becomes more resilient to centralization. This diversity makes it difficult for any single entity to control a significant percentage of the mining power.
Double Spend Prevention:
Each transaction is tied to previous signatures and transaction data, creating a robust record that can be easily verified during parsing.
If a user attempts to double spend, the network's consensus mechanism will flag the conflicting transactions during the parsing stage, preventing them from being added to the blockchain.
The use of serialized mining rounds ensures that only one block is accepted at a time, with each new block dependent on the data from the previous one. This serialization significantly reduces the chances of double spending since any conflicting transactions would not be valid due to the linkage to prior blocks.
Signature Context
Each transaction ties back to the previous transaction’s signature, creating a unique context for validation. The system incorporates both the transaction hash and the previous signature in the signing process, ensuring contextual linking.
Replay Attack Mitigation
By incorporating the previous signature into every transaction, the system significantly reduces the likelihood of successful replay attacks. An attacker would have to manipulate the context of a valid transaction, which is tightly controlled.
Integrity Through Aggregation
Aggregating signatures across transactions enhances trust and ensures that all participant signatures are valid, creating a robust validation mechanism for each block.
Strengths of the System
Mitigation of Signature Ambiguity:
Hashing each transaction before signing prevents ambiguity in signature validation, ensuring clear and unique representations.
Enhanced Security Against Replay Attacks:
By tying each transaction to the previous signature, the system reduces the likelihood of replay attacks.
Chain of Trust:
The sequential linking of transactions establishes a chain of trust, reinforcing the integrity of the blockchain.
Efficient Data Representation:
Using Huffman coding improves transaction processing efficiency, enabling better performance without sacrificing security.
Distributed Trust Model:
The requirement for multiple signatures reduces reliance on any single participant, enhancing resilience against collusion and single points of failure.
Collective Network Performance:
By encouraging users to repurpose old technology (like old laptops and smartphones) for mining and data relaying, the network becomes more robust. Users' contributions to bandwidth and processing power enhance the network's speed and efficiency.
Areas of Weakness and Recommendations
Hash Function Security:
The system's security relies heavily on the hash function used. Ensure the use of robust cryptographic hash functions (e.g., SHA-256 or SHA-3) to prevent collision attacks.
Signature Aggregation Complexity:
The aggregation process must be clearly defined to avoid errors in signature validation. Implement checks and balances for validating aggregated signatures.
BLS Single Signature Context:
To avoid potential vulnerabilities, consider implementing nonce mechanisms or additional unique identifiers for each transaction.
Replay Attack Mitigation:
Additional context checks, such as timestamps or nonces, can further ensure that each transaction is validated against its intended context.
Shared Dictionary Vulnerability:
Secure management of the shared dictionary is essential. Consider using a hashing mechanism for dictionary entries to detect unauthorized modifications.
Potential for Denial of Service (DoS):
Implement rate limiting and transaction validation checks to mitigate DoS attack risks.
Complexity of Signature Verification:
Thoroughly test the signature verification process to identify potential weaknesses and ensure robustness.
Cryptographic Assumptions:
Stay informed about developments in cryptographic research and adapt to newer, more secure signature schemes if necessary.
Conclusion
The proposed blockchain system effectively integrates innovative methods to address challenges associated with BLS multi-signature schemes, transaction integrity, efficient data encoding, and robust double spending prevention. By linking transactions contextually, employing Huffman coding, and implementing a decentralized mining framework, the system establishes a resilient and secure foundation for transactions. Additionally, the collective responsibility of network participants enhances network efficiency and resilience, creating a community-oriented ecosystem.
This combination of technological innovation and social responsibility positions the system for a sustainable future, empowering participants to contribute to a faster and more secure decentralized network while benefiting from their involvement.
IMO it is rather brave decision to ues NodeJS for this, I would really want to see it in action.
Once you have a website and whitepaper, please share them with us. It will be interesting.
Once you have a website and whitepaper, please share them with us. It will be interesting.
What resources are being shared? Social media can be applied to network or storage resources.
The next AR/FIL?
The next AR/FIL?
each user is a seed for his own content. for the immediate future, the idea is that you are hosting the content you wish to share on the network (like pics, vids, music, art, journalism, state secrets, your nanna's rhubarb jelly recipe)
in the future
you will be able to host
video streams
apps
services
games
ML models
modular neural network nodes
there is a lot more planned but it depends on user participation. i feed off of your enthusiasm. give me love i give you magic!
i had a bit of a snafu with my cloud servers so i had to put the deom off until tonight. please join the live stream where i can fully explain everything and answer your questions.
thanks
What resources are being shared? Social media can be applied to network or storage resources.
The next AR/FIL?
The next AR/FIL?
Im looking forward to it I'm interested to see what you got going on here buddy
Create discord channel so we can support, chat with ease. ./Cheershttps://discord.com/channels/1279883883734630442/1279883883734630445
here you go
LINK is invalid
Create discord channel so we can support, chat with ease. ./Cheershttps://discord.com/channels/1279883883734630442/1279883883734630445
here you go
We are going to give a real value to one of the most valuables assets among the humanity: Artists.
Inventors and programmers are artist too. Any kind of language is art.
Inventors and programmers are artist too. Any kind of language is art.
I send the Discord Request. Love Discord. Any links to the project? Sounds like this has a great jumping off point. Thanks for the announcement.
Create discord channel so we can support, chat with ease. ./Cheers
EXACTLY! you got it my friend. bubble is a real currency with a built in use case and monetary balanceing baked in like the federal reserve. the coins will always be useful. the likes have a dual purpose too. they are held in the mempool and processed in batches, this both reduces bloat AND ties coins up in an unspendable state for a long period which reduces the available supply (hopefully by 5-10%) making price stability easier to achieve 
this has been something i have been formulating almost my entire life and crypto is just a way to experiment.
i literally went to college and earned 2 engineering degrees (software systems) with 0 prior coding experience and spent 3.7 years building it
this has been something i have been formulating almost my entire life and crypto is just a way to experiment.
i literally went to college and earned 2 engineering degrees (software systems) with 0 prior coding experience and spent 3.7 years building it
Got it. The engagement is what can make it profitable. 
im not sure what you are asking. my comments are intended to describe the technical limitations of a p2p stream. what im describing is how the (data) swarm would work around the stream. there is no monetary reward for the stream other than the revenue generated through likes and follows earned during the broadcast or as a post on the network.
the reward scheme is as always POW mining, we just added a compression round (second reward) for mining the smallest block size as well as the hash difficulty reward, so there is a mining reward, a compression reward, and a third smaller random reward given to a random post made during the block round. but all posts can be liked by a viewer, which is like a way of supporting content creators, and follows also are paid by the "follower" to the creator.
this money generated through likes and follows is "taxed" and the TAX gets "burned" as a way to control inflation. this is how we regulate the economy.
so
miners and "huffers" (compression) and random content creators " mine" the coins into existence
they support the creators
the tax is burned
the burn is recycled
the mners mine new coins
this should theoretically give us a supply which both infinitely produces new coin at the bottom and also remains a limited supply that dosen't grow beyond the cap ... in theory anyway
the reward scheme is as always POW mining, we just added a compression round (second reward) for mining the smallest block size as well as the hash difficulty reward, so there is a mining reward, a compression reward, and a third smaller random reward given to a random post made during the block round. but all posts can be liked by a viewer, which is like a way of supporting content creators, and follows also are paid by the "follower" to the creator.
this money generated through likes and follows is "taxed" and the TAX gets "burned" as a way to control inflation. this is how we regulate the economy.
so
miners and "huffers" (compression) and random content creators " mine" the coins into existence
they support the creators
the tax is burned
the burn is recycled
the mners mine new coins
this should theoretically give us a supply which both infinitely produces new coin at the bottom and also remains a limited supply that dosen't grow beyond the cap ... in theory anyway
So basically the most viewed streamer (let's call it empathic) will be the most rewarded due its amount of seeders?
yes! but, because there is no central server, the stream is like a daisy chain where it is hosted and shared to a few people who then share it on in the swarm. so each viewer is also a seed for the stream
so like this:
host=> viewer => another viewer => so on
does this make sense
this is still in development however and will not be part of the initial launch. i am focusing on polishing up the features i have previously mentioned and outlined in my initial design plans all those years ago
so like this:
host=> viewer => another viewer => so on
does this make sense
this is still in development however and will not be part of the initial launch. i am focusing on polishing up the features i have previously mentioned and outlined in my initial design plans all those years ago
Jump to: