Xxl channel p2p
r/Ligue1: Le subreddit français du ballon rond !
2011.02.21 00:23 Ribsduff r/Ligue1: Le subreddit français du ballon rond !
News & Discussions football : Ligue 1, Ligue 2, les Bleus mais aussi toutes les compétitions françaises et étrangères ainsi que tout ce qui touche au monde du football.
2009.09.15 03:56 kennyreborn Hyderabad
A place for Hyderabadi redditors to hangout, discuss the city, exchange information about incoming events and whatever else strikes our fancy.
2012.11.19 09:35 coolerheadprevails Full Movies On YouTube
Full movies on YouTube
2024.05.13 16:30 cryptovechkin Breaking the Chains of Obscurity and Unleashing Pepe's Pet: $Nitefeeder [1M Market Cap][70 Days Old]
![Breaking the Chains of Obscurity and Unleashing Pepe's Pet: $Nitefeeder [1M Market Cap][70 Days Old]](https://external-preview.redd.it/yU2Mp6HQML9yCUFN4Kb_kLS01xOc4DSLXWU6fwI4k-k.png?width=640&crop=smart&auto=webp&s=4210904a9b1998f0401a961f07f6ca9ef712a09a "Breaking the Chains of Obscurity and Unleashing Pepe's Pet: $Nitefeeder [1M Market Cap][70 Days Old]") | https://preview.redd.it/t7oeosco810d1.jpg?width=640&format=pjpg&auto=webp&s=4909b1057159edb30f8503ea0d312e7e53a50a7e submitted by cryptovechkin to memecoins [link] [comments] By now you've likely heard of Kendu, but did you know that the #3 holder of Kendu also happens to be the #1 holder of Nitefeeder? How did they have the foresight to invest in Kendu on launch at $100k market cap and in Nitefeeder from day one? Take a moment to let that sink in. Some of you may recall my username from when I first shilled DFNDR ($500k to $38m), PalmAI ($450k to $160m for a 355x), or even REDO (from $300k to $100m+ for a 300x+) in select alpha Telegram channels. I don't endorse just about anything unless I have unwavering conviction (and a touch of alpha, of course) and there's a deliberate reason why I waited until this exact moment to discuss Nitefeeder. Now that I have your attention, stay awhile and listen. What makes a meme coin successful? Is it the strength of its community, its compelling narrative, or perhaps the innovative features and use cases it offers? Could it be the result of savvy marketing and hype, long-term viability or is success simply a matter of luck and timing? I bet you've heard it countless times: "Buy X meme coin because the community is strong, the narrative is compelling, the marketing is insane!" But how often are these claims backed up with solid facts, numbers, and evidence? In a crowded marketplace with tens of thousands of coins boasting similar "traits," what truly distinguishes your meme coin? Let's take a deep dive to uncover the real value beneath the hype. NarrativeWhat is Nitefeeder? Well, simply put, Nitefeeder is Pepe's one and only pet which can be found on page 27 of Matt Furie's Boys Club Comic. Now, how well do "pet" meme coins do compared to their predecessors? Let's compare a few examples:
CommunityWhat makes a strong community?Is it the fact that over $100k in Nitefeeder and ETH was donated to the multisig community marketing wallet? What about the dedication of a community member who flew across continents to engage in face-to-face discussions about Nitefeeder with none other than Matt Furie himself? Or is it simply the unpaid devs who contributed their time to craft stunning websites, and artists who passionately created brand-new logos? And let's not forget the creativity and passion of a volunteer who took it upon themselves to craft their own rendition of the Nitefeeder comic that they will continue to release regularly. I have been in the crypto space for almost 10 years and I definitely could never have imagined myself creating a Reddit account, laying out my research, and advocating for a meme coin. Yet, here I am, realizing the strong connections I've formed with Nitefeeder community members I've never even met. It's a true testament to the power of community and the unexpected journeys it can lead us on. Long-Term ViabilityAs we all know, meme coins often rise and fall to the fluctuating strength of their narratives. But what's the secret ingredient that keeps the hype alive? Who will step up to fund the ongoing marketing efforts of a meme coin with a 0/0 tax structure? The 30+ whales who have generously contributed to the marketing wallet can't sustain it forever—or perhaps one of them can, but let's save that discussion for another day (IYKYK).Our community developers are hard at work creating three exciting mini-games featuring Nitefeeder, promising endless entertainment and a long-term revenue stream. And that's just scratching the surface—our main P2P game is already in the works. Now, the decision is yours. Do you seize the chance to join a meme coin while the market is calm, or do you wait until FOMO kicks in, realizing you missed out on a golden opportunity? LuckWhen a coin pumps like crazy in a short period of time, it's often attributed to sheer luck and perfect timing. However, luck isn't our focus; we're forging our own luck. Pepe's legacy continues, Boys Club endures, and Nitefeeder sure as hell isn't going to stop either.Join us on Telegram, or better yet, join the exclusive whale group where untapped alpha awaits, far beyond the confines of this post. https://www.dextools.io/app/en/ethepair-explore0x1ce1f63b584b87d0f3706bfbb2be881270859f0b?t=1715306287962 CA: 0x85f7cfe910393fb5593c65230622aa597e4223f1 |
2024.05.12 04:19 pixelsimg1234567 Classification of Cyber Crime
 | https://preview.redd.it/1xyj6hrvnwzc1.jpg?width=800&format=pjpg&auto=webp&s=55043a0296ee1e0f0c720d8f9bbc29824e1dab30 submitted by pixelsimg1234567 to u/pixelsimg1234567 [link] [comments] Classification of Cyber Crime we will read about side train classification, how many textures can we classify cyber crime, whereas we can classify cyber crime as total notes murder. First of all, there is cyber stalking. Now what is the meaning of stalking in general? It happens that following any person to humiliate him, to intimidate him or her, this is a general thing. This topic is that cyber stalking means that to humiliate a person, to turn him on the internet, to intimidate him or her. Or by the use of any information technology, then it comes under cyber stalking category, then cyber stalking is the act of harassing or threatening another person over the internet, internet users rules, any information technology, Tuesday, now what is cyber stalking in general, internet e -Mail chat room is the mother of them all, it is targeted at any particular person and he is harassed. Okay, now in this topic, what happens in cyber stalking in general is that what remains in this topic is to follow the individual. Facebook starts following the profile and collects information about it so that it can send it to the person on the phone. Candy Crush 233 People Subscribe in Different Ways Conduct That Those Three Different Ways of Conducting Fiber So the first thing he does is to send an email to the individual victim here. He can intimidate her, send her wrong photos, scare her, now what happens in this talking to internet is that by publicly stockpiling, he can SMS anything in the name of the victim, on that phone number or email ID or photo book, publicly. He writes it down and shocks her in her private space, exposes you publicly, starts intimidating and threatening her. Now what is there in this Chowk Nehru Computer that he takes the stock of the victim's computer and gets her computer. Then he starts accessing his information and starts threatening him. Now whatever is in it, it should be technical. Not everyone can do stock through computer. Technical, who would know that any manager can access OP's computer? How to hack the same computer, one can do that topic, so this is the first classification, cyber stalking, now the second classification is that now what is the simple meaning of hacking, baiting, unauthorized access of another computer, taking unauthorized access of someone else's computer means you have this The person who is taxed is not authorized to use someone else's computer, he is not a person, still he takes away his rights somehow or the other. Also Read- p2p trading se bank account kese unfreeze karaye So what would you say to him that he has hacked his computer. Now there are other hacking prevention tools like firewall, intuition detection system, okay, whatever they are, they can control the acting, prevent it and protect your computer. You can save your computer if your computer is not hacked, then this affair was in Bigg Boss comment. Intrusion detection system, these two breaks are generally installed quantum so that your computer is computer virus till 2030 classification. Now generally we call it virus, which virus is virus, why our I click on you and it keeps on making me human. Human means that by doing the computer itself, it is a virus. In a computer, it is as if it infects other viruses and programs like itself. By corrupting the computer program files, it becomes a computer virus. Computer program: This is a computer program which is busy in replicating itself. The monkey is replicating the dandruff in the application. The ready-applicator is doing it, that is, it is generating another copy of itself. Also Read- how to unfreeze bank account from gujarat cyber cell Okay, so this program is gambling and new programs which are generated by plants and corrupt the programs on the other side of the computer. And where is the computer virus in your computer? First of all, computer virus is computer proof directly in your computer. It seems that if you are using the internet by subscribing to it, then also there is a computer virus in your computer. Classification from this tree means that Kabir is sending you some message about all these matters and you feel as if he is The message is from my bank but listen to the message that it is not coming from your bank. Now if I have sent a message to you, then the same process would open to phishing attacks. If the practice of sending road development communication means sending fraudulent messages, Middle aged appear to come from reputed to solve send that message how should it appear why rapid source MP3 is from table spoon it is usually done through email and generally what happens is that mother becomes professional through email just like this meaning advice you are engaged host is this Our bank honey, in which category does fashion cutting come? Now people question why this income is for the purpose of gaming the user's sensitive information like credit card information or login information or bank details. Yaksha question us on Classification and Denial of Service Step by Step is that a particular website shopping Click on Flipkart's website and this side of mine and it turned out that some extras and subscribe on other websites by using subscribe so that Subscribe Our Channel Not Subscribe English What will happen with this, Also Read- bank account freeze by telanagana if they go to Amazon and purchase only on the good download vultures of Flipkart, then what happens in Denial of Service Tax is that each and every A remains closed and they overload their computer organization. Make it so that the users do not use it. Service Tax is the traffic machine on which is to make available for the attack. If they can do this then the attack is that they can generate a lot of traffic, that is, they will send a lot of requests on it and the traffic machine will be the machine, that is the second one. Don't get it and it will get overloaded in a way and will get held, now what is the example of overloading shopping website in the festive season, so the idea was that if you like this blog then you have to like my blog . |
2024.05.11 00:07 Small-Phone-6154 ONVIF NVR: Only 2 profiles available / some profiles missing
 | Hi all, hoping someone can help... submitted by Small-Phone-6154 to Scrypted [link] [comments] I have four PoE cameras connected to the following NVR, with the cameras connected directly to / behind the NVR (i.e. the cameras are on a local network / subnet with IP addresses issued by the NVR). The cameras and NVR are branded 'FVS', but I believe FVS is an 'own-brand' and the underlying manufacturer is probably one of the common Chinese brands. Cameras: FV-PRO 9584S3B-2.8 - NEW 4K 8MP Enhanced IP Mini Eyeball with IR LED & Built-in Audio (fvs-cctv.com) NVR: FV-PRO DVR2104-4K - 8MP 4K Lite Hybrid 4 Channel P2P Pentaplex DVR (fvs-cctv.com) Details of the NVR web client and Windows plug-in are appended below in case relevant. Because I don't know the underlying manufacturer, I've used the ONVIF plugin and then followed the guidance in the ONVIF plug-in readme file: ONVIF NVRs are not directly supported yet. To access cameras behind an NVR, add the NVR once per camera, and select the correct camera channel.This has worked perfectly... except only two of the four cameras / channels are available. I see the following profiles available in Scrypted:
Has anyone encountered a similar problem and found a solution? I have checked settings on the NVR web client and all the cameras / channels are configured the same... so I am wondering if this is an issue with the NVR only 'pushing' 2 cameras to Scrypted or Scrypted only 'pulling' 2 cameras from the NVR. Alternatively, if anyone knows who the underlying manufacturer may be, I could try using the applicable manufacturer plug-in rather than ONVIF... which might fix this issue? Grateful for any help! Appendix The NVR runs some unbranded web client which looks like this: https://preview.redd.it/s8bp8ovf9ozc1.png?width=1536&format=png&auto=webp&s=8b80d5f57c3e54946e7a56859afd38b93575fafb I had to install a Windows plug-in as follows: https://preview.redd.it/ronu96gw8ozc1.png?width=806&format=png&auto=webp&s=610b81f77333a255489e15e079414cd08ada67f8 |
2024.05.10 23:26 Street-Razzmatazz978 Dev Release 26
May 8, 2024 Dev Release 26 Greeting BlockDAG Community,
As mentioned in previous update, as a part of substream implementation in blockDAG today we're implementating request-response protocol along with notification protocol. In this technical post, we'll delve into the details of how request-response protocols function within substreams and it's importance in BlockDAG project.
A quick recap of what substreams are and the purpose of request-response protocol Substreams are the virtual connections or data transmission channels logically created between the network nodes in a BlockDAG layout. Consequently, the existence of these side-chains enables peers to trade data and store the blocks and transactions as they are relayed across the network. For more details refer to the previous post here . Purpose: Substream request-response protocol is tailored to ensure the continuation of sophisticated information querying and retrieval from peers within a distributed network. This protocol is an indispensable part of the whole cycle in tasks like block validation, consensus making and data synchronization which can result in emergence of a BlockDAG. Each request is performed in a new separate substream.
Elements of Request-Response method The essential elements of Request-Response method:
Initiation of Requests: Node start a search by sending a special formatted request to the node it is directly connected to within a sub stream. This type of message usually contains the details of the data being requested, with inclusive participation of population, stakeholders and organizations in making a decision which means the entire history of who sent how much money to whom is recorded for everyone to see (e.g., a specific transaction or a certain block). Handling Requests: In case of a request from a peer node, the node processes it and draws up an appropriate answer. And the answer is again to be sent back to the client via the same substream. Response Handling: The node delivering a response will be noticed by the requesting node and the information inside it will be processed. It might be a matter of validating the block, entering it into the local register or subsequently transmitting the received data across the network. Algorithm to implement the request-response protocol Deployment of request-response protocol as a primary means of internode communication in substreams within BlockDAG network entails several steps and concerns which must be taken into account to avoid potential issues. Below is a technical algorithm outline detailing how this protocol can be implemented:
Message Structures: Create message structures that are standardized by which nodes can communicate every time with their neighbors through requests and responses. These messages should have available identifiers, data payloads, and metadata. A distinguishing code is known as an identifier; this facilitates quick tracking and identification of danger.
Substream Establishment: Create link-branches between the elements to provide direct information channels subheadings. This is enabled by the use of TCP/IP or P2P protocols which can be customized.
Requester Node Behavior: Send Request: The situation is that the when a node requires certain data, the node determines the shortest path by using the distributed network and it sends the data request to the node with the highest opportunity to generate the block. By creating a request message with a block or transaction format, it sends it via a substream to the peer node with which connection has been previously established. Wait for Response: Requester node patiently waits for reply message from the peer node, after those request messages are sent. It also a timeout option to deal with the cases where no response has been received within a timely manner.
Responder Node Behavior: Receive Request: The peer node is the receiving get source from the substream. Process Request: On receiving a query, the peer node examines it, in case the data is available it will be retrieved and prepared for a reply before the acknowledgement message is sent by the node. Send Response: The peer node sends an acknowledgment message to the querier node using the identical substream as the one used to forward the queries.
Error Handling: Develop mechanisms of error handling that take care of communication failures, timeouts, or incorrect requests. To do this, we will gradually increase the complexity of our systems and test their readiness by performing stress tests. Retry Mechanism: The requester node has to react in such a manner that within the time frame that has been set, if no reply is received, it retries the request, or the process is handled accordingly.
Asynchronous Processing: Adopt asynchronous programming techniques to solve the issue of various simultaneous requests handling efficiency. Implement callback operations or event handlers to react to response messages, processing them as they come in and keeping instance as responsive as it is.
Notification protocol in BlockDAG It's also a part of above protocol's implementation, below is a quick summary of how Notification protocol would work.
As a handshake message is the first message which is sent when a substream is opened, it has the content of a protocol. The head message must be prefixed with a 2+bytes length number which was encoded with the LEB128. The encrypted handshake message can have a length of 0 which for the sender simply means that a single 0 must be sent. The receiver then sends either back a LEB128-prefixed R-ack handshake to the substream closure, or answers with its own specific protocol handshake that begins with a LEB128. Along with it, the message length will also be of 0. So the receiver has to send back a single 0. When you finished shaking hands, your communications protocol becomes unidirectional. The stream can only be revealed if the node which initiated the substream pushes out notification. If the remote also wants to send notifications, it has to open its own unidirectional substream, since the main transmission has to be multicast. Every alert has to start with an LEB128(a)-translated length. All codecs that art transcoded for each protocol are different from the other. Both parties, either of them can demonstrate that it doesn't want to have a notification substream by closing their writing-side. Besides, the counter message should surface immediately following the other party`s writing side. The sc-network API enables the registration of notification protocols as user-defined entities. sc-network will be trying automatically for each node substream to open where the previous counterpart from Legacy Substream will be opened by it. Then comes the Handshake thing without conscious thought.What is currently in place, for a manner of backward-compatibility, a group of notification protocols are joined with the legacy Substrate branch. Additionally, the handshake message is hardcoded to be a single 8-bits integer representing the role of the node: To run an accomplished full node, you shall set aside 1 GB of memory, while for much less achieved ones, 32 MB will do the secret. 2 for concealing a light source on node lighting. 4 for an authority. In addition, in the future, these restrictions will be totally scrapped.
Algorithm to implement the notification protocol Sending a Notification: A node triggers a notification event by invoking notify_peers() with specific event_type and the information in it. This function forwards the information message contain event type, data, and the event issuers address to all the peer nodes connected.
Receiving and Processing Notifications: Every peer node receives the alert sent at render_headers() method. The receiving node examines the relevance and is configured to carry out actions based on the event type.
Example implementation:
node2 = BlockDAGNode(node_id=2)
# Add peer nodes for communication
node1.peer_nodes.append(node2)
node2.peer_nodes.append(node1)
# Simulate notification - Node 1 notifies peers about a new block
new_block = Block(block_id=1, transactions=["Tx1", "Tx2"], parent_blocks=[]) node1.notify_peers(event_type="new_block_received", event_data=new_block)
# Node 2 receives and processes the notification
# This triggers Node 2 to process the new block received from Node 1
# The notification protocol can be extended to handle various types of events and data
Next steps After the successful implementation of the communication protocols between the nodes and a notification service it's essential to sync all the nodes with the same information to maintain a consistency in the ledger. Therefore, the next step after this would be working on the syncing process and implementing the same.
Share this post Copy link Prev Post Next Post
submitted by Street-Razzmatazz978 to BDAGminer [link] [comments]
As mentioned in previous update, as a part of substream implementation in blockDAG today we're implementating request-response protocol along with notification protocol. In this technical post, we'll delve into the details of how request-response protocols function within substreams and it's importance in BlockDAG project.
A quick recap of what substreams are and the purpose of request-response protocol Substreams are the virtual connections or data transmission channels logically created between the network nodes in a BlockDAG layout. Consequently, the existence of these side-chains enables peers to trade data and store the blocks and transactions as they are relayed across the network. For more details refer to the previous post here . Purpose: Substream request-response protocol is tailored to ensure the continuation of sophisticated information querying and retrieval from peers within a distributed network. This protocol is an indispensable part of the whole cycle in tasks like block validation, consensus making and data synchronization which can result in emergence of a BlockDAG. Each request is performed in a new separate substream.
Elements of Request-Response method The essential elements of Request-Response method:
Initiation of Requests: Node start a search by sending a special formatted request to the node it is directly connected to within a sub stream. This type of message usually contains the details of the data being requested, with inclusive participation of population, stakeholders and organizations in making a decision which means the entire history of who sent how much money to whom is recorded for everyone to see (e.g., a specific transaction or a certain block). Handling Requests: In case of a request from a peer node, the node processes it and draws up an appropriate answer. And the answer is again to be sent back to the client via the same substream. Response Handling: The node delivering a response will be noticed by the requesting node and the information inside it will be processed. It might be a matter of validating the block, entering it into the local register or subsequently transmitting the received data across the network. Algorithm to implement the request-response protocol Deployment of request-response protocol as a primary means of internode communication in substreams within BlockDAG network entails several steps and concerns which must be taken into account to avoid potential issues. Below is a technical algorithm outline detailing how this protocol can be implemented:
Message Structures: Create message structures that are standardized by which nodes can communicate every time with their neighbors through requests and responses. These messages should have available identifiers, data payloads, and metadata. A distinguishing code is known as an identifier; this facilitates quick tracking and identification of danger.
Substream Establishment: Create link-branches between the elements to provide direct information channels subheadings. This is enabled by the use of TCP/IP or P2P protocols which can be customized.
Requester Node Behavior: Send Request: The situation is that the when a node requires certain data, the node determines the shortest path by using the distributed network and it sends the data request to the node with the highest opportunity to generate the block. By creating a request message with a block or transaction format, it sends it via a substream to the peer node with which connection has been previously established. Wait for Response: Requester node patiently waits for reply message from the peer node, after those request messages are sent. It also a timeout option to deal with the cases where no response has been received within a timely manner.
Responder Node Behavior: Receive Request: The peer node is the receiving get source from the substream. Process Request: On receiving a query, the peer node examines it, in case the data is available it will be retrieved and prepared for a reply before the acknowledgement message is sent by the node. Send Response: The peer node sends an acknowledgment message to the querier node using the identical substream as the one used to forward the queries.
Error Handling: Develop mechanisms of error handling that take care of communication failures, timeouts, or incorrect requests. To do this, we will gradually increase the complexity of our systems and test their readiness by performing stress tests. Retry Mechanism: The requester node has to react in such a manner that within the time frame that has been set, if no reply is received, it retries the request, or the process is handled accordingly.
Asynchronous Processing: Adopt asynchronous programming techniques to solve the issue of various simultaneous requests handling efficiency. Implement callback operations or event handlers to react to response messages, processing them as they come in and keeping instance as responsive as it is.
Notification protocol in BlockDAG It's also a part of above protocol's implementation, below is a quick summary of how Notification protocol would work.
As a handshake message is the first message which is sent when a substream is opened, it has the content of a protocol. The head message must be prefixed with a 2+bytes length number which was encoded with the LEB128. The encrypted handshake message can have a length of 0 which for the sender simply means that a single 0 must be sent. The receiver then sends either back a LEB128-prefixed R-ack handshake to the substream closure, or answers with its own specific protocol handshake that begins with a LEB128. Along with it, the message length will also be of 0. So the receiver has to send back a single 0. When you finished shaking hands, your communications protocol becomes unidirectional. The stream can only be revealed if the node which initiated the substream pushes out notification. If the remote also wants to send notifications, it has to open its own unidirectional substream, since the main transmission has to be multicast. Every alert has to start with an LEB128(a)-translated length. All codecs that art transcoded for each protocol are different from the other. Both parties, either of them can demonstrate that it doesn't want to have a notification substream by closing their writing-side. Besides, the counter message should surface immediately following the other party`s writing side. The sc-network API enables the registration of notification protocols as user-defined entities. sc-network will be trying automatically for each node substream to open where the previous counterpart from Legacy Substream will be opened by it. Then comes the Handshake thing without conscious thought.What is currently in place, for a manner of backward-compatibility, a group of notification protocols are joined with the legacy Substrate branch. Additionally, the handshake message is hardcoded to be a single 8-bits integer representing the role of the node: To run an accomplished full node, you shall set aside 1 GB of memory, while for much less achieved ones, 32 MB will do the secret. 2 for concealing a light source on node lighting. 4 for an authority. In addition, in the future, these restrictions will be totally scrapped.
Algorithm to implement the notification protocol Sending a Notification: A node triggers a notification event by invoking notify_peers() with specific event_type and the information in it. This function forwards the information message contain event type, data, and the event issuers address to all the peer nodes connected.
Receiving and Processing Notifications: Every peer node receives the alert sent at render_headers() method. The receiving node examines the relevance and is configured to carry out actions based on the event type.
Example implementation:
# Create BlockDAGnodes node1 = BlockDAGNode(node_id=1)
node2 = BlockDAGNode(node_id=2)
# Add peer nodes for communication
node1.peer_nodes.append(node2)
node2.peer_nodes.append(node1)
# Simulate notification - Node 1 notifies peers about a new block
new_block = Block(block_id=1, transactions=["Tx1", "Tx2"], parent_blocks=[]) node1.notify_peers(event_type="new_block_received", event_data=new_block)
# Node 2 receives and processes the notification
# This triggers Node 2 to process the new block received from Node 1
# The notification protocol can be extended to handle various types of events and data
Next steps After the successful implementation of the communication protocols between the nodes and a notification service it's essential to sync all the nodes with the same information to maintain a consistency in the ledger. Therefore, the next step after this would be working on the syncing process and implementing the same.
Share this post Copy link Prev Post Next Post
2024.05.10 14:48 KristineJakovleva How to start a money remittance or money transfer business
 | Starting a remittance or money transfer business is a venture that requires careful planning, adherence to regulatory frameworks, and strategic partnerships. In this article, we explore the concepts of money remittance and transfer, examining various types of remittance services. Additionally, we offer a guide outlining the step-by-step process to establish a successful remittance or money transfer business. submitted by KristineJakovleva to u/KristineJakovleva [link] [comments] https://preview.redd.it/gb1c4e7nhlzc1.jpg?width=1200&format=pjpg&auto=webp&s=596523a333c301fc33c83dd4929c643778238c3b What is money remittance?Money remittance involves sending money from one location to another, typically across borders, to meet financial needs or fulfil payment obligations. This financial service is vital for individuals who must send funds to family members, friends, or others in different regions or countries. Money remittance can occur through various channels, such as banks, dedicated remittance providers, online platforms, or mobile applications.The sender initiates the transfer by providing necessary details about the recipient and selecting the preferred transfer method. The recipient can access the transferred funds through local financial institutions or designated payout locations. Money remittance is crucial in supporting global financial connectivity and addressing the diverse financial requirements of individuals and businesses worldwide. These services contribute to financial inclusion by providing accessible and efficient channels for individuals to send and receive money globally, overcoming geographical barriers and enhancing overall economic well-being. What is a money transfer?A money transfer refers to moving funds from one individual or entity to another. This financial transaction can occur through various channels, including banks, online platforms, money transfer services, or traditional methods. Money transfers are commonly utilised for diverse purposes, such as sending funds to family members, making payments, conducting business transactions, or meeting financial needs across borders.The process typically begins with a sender initiating the transfer, specifying the recipient, and selecting a preferred transfer method, such as wire transfers, online transfers, mobile payments, or remittance services. The term ‘money transfer’ also encompasses credit/debit card transfers, where funds move from one card to another credit/debit card, a bank account, or a merchant. How remittance worksRemittance is a financial process that enables the transfer of money from one location to another. The sender initiates the transaction through a remittance service provider, a traditional brick-and-mortar agency, an online platform, or a mobile application. The sender provides necessary details, such as the recipient’s name, location, and transfer amount.The remittance service processes the transaction, converting funds into the desired currency if necessary and transfers the money to the recipient. The recipient can then collect the funds through various channels, including cash pickup points, bank accounts, mobile wallets, or even opt for home delivery, depending on the chosen service and the options provided by the remittance provider. The entire process is facilitated by a network of financial institutions and payment service providers to ensure a secure and efficient transfer of funds across borders. Forms of money transfersWhat are the types of money transfers?1. Bank Transfer:Easily facilitated through online banking or apps, bank transfers are common. In the UK, Bacs, CHAPS, or Faster Payments, and in the EEA, SEPA payments support both one-off and regular transfers.2. Wire Transfer:Ideal for international transfers, wire transfers move money between two unlinked bank accounts, with the bank serving as an intermediary.3. In-Person Transfer:Specialised money transfer services like Western Union facilitate in-person transactions. This method accommodates recipients without bank accounts, allowing them to collect funds in cash at a nearby agent location.How can money remittance be executed?Money remittance can be executed through various methods, providing consumers with diverse options to suit their preferences:1. Through a Bank or Financial Institution:Funds can be transferred from the sender’s bank account to another using online banking, digital services, a banking app, or visiting a branch. Essential details include the recipient’s account name, sort code, and account number. Customers may need the recipient’s IBAN or SWIFT/BIC code for international transfers.2. Through a Specialised Money Transfer Company:Companies like Western Union offer multiple methods for transferring money within many countries. Customers can choose between online transfers or visiting an agent’s location for an in-person transaction. Depending on the transfer type, customers will need the recipient’s details and possibly a government-issued ID for verification, ensuring a swift and secure delivery.3. Through a Payment App:Remittance can be provided through a payment app for convenient on-the-go transfers. Customers can seamlessly send money directly to a loved one’s bank account using their debit or credit card. Alternatively, funds can be transferred for pickup at a local or international location.4. To the Receiver’s Phone:Money can be sent directly to their phone to provide the recipient with immediate access to funds. Depending on their location and mobile operator, funds can be directed to the recipient’s mobile wallet, allowing for instant spending.Types of money transfer or remittance businessesMoney transfer or remittance businesses encompass various types, each tailored to meet individuals’ and businesses’ specific needs and preferences. These include:1. Traditional Brick-and-Mortar Services:Operating through physical locations such as banks or dedicated remittance centres, these services allow customers to send money in person.2. Online Money Transfer Platforms:These platforms have gained popularity, enabling users to initiate transactions through web-based interfaces or mobile applications, providing convenience and accessibility.3. Mobile Money Services:Leveraging mobile phone networks, these services facilitate transfers, particularly in regions with limited access to traditional banking.4. Peer-to-Peer (P2P) Payment Platforms:Individuals can send funds directly to each other using digital wallets or bank accounts through these platforms.5. Cryptocurrency-Based Remittance Services:Utilising blockchain technology for secure and decentralised transactions, these services offer an alternative to traditional methods.The diverse landscape of money transfer businesses reflects the financial services sector’s evolving preferences and technological advancements. Traditional brick-and-mortar remittance servicesTraditional brick-and-mortar remittance services have served as the cornerstone of cross-border financial transactions for an extended period. These physical establishments, commonly situated in local communities, serve as a familiar and accessible channel for individuals to send and receive money. Customers typically visit these locations to initiate transactions, relying on face-to-face interactions with service agents. Renowned for their reliability and trustworthiness, these establishments offer a comforting in-person experience, especially for those less familiar with digital transactions. Although lacking the convenience of online platforms, brick-and-mortar remittance services remain indispensable in catering to populations with limited access to technology or those who prefer the tangible and personal nature of in-person transactions.Online money remittance businessesOnline money remittance businesses have revolutionised the financial landscape, offering individuals a convenient and efficient way to send money globally. These digital platforms utilise web-based interfaces or mobile applications, enabling users to initiate transactions from the comfort of their homes or on the go. With secure and streamlined processes, online remittance services provide speed and accessibility, diminishing the reliance on traditional brick-and-mortar methods. Users can fund transfers using various payment options, including bank accounts, credit cards, or digital wallets. Furthermore, real-time tracking features empower senders and recipients to monitor the status of their transactions. The growth of online money remittance businesses underscores the industry’s commitment to leveraging technology for enhanced financial inclusion and seamless cross-border transactions.The international money transfer industry overviewThe international money transfer industry is pivotal in facilitating global financial transactions and fostering connections among individuals, businesses, and economies across borders. Technological advancements have significantly reduced traditional barriers, enabling faster, more accessible, cost-effective remittance services.As of 2020, the global remittance market was valued at $701.93 billion, and it is expected to reach $1,227.22 billion by 2030, projecting a Compound Annual Growth Rate (CAGR) of 5.7% from 2021 to 2030. Major players in the remittance market include Bank of America, Citigroup, JPMorgan Chase & Co., MoneyGram International, RIA Financial Services, Wise, UAE Exchange, Wells Fargo, Western Union, and XOOM. These players have implemented diverse strategies to strengthen their market presence, such as expanding product portfolios, engaging in mergers and acquisitions, forming agreements, extending geographical reach, and fostering collaborations. What you need to start a digital money remittance or money transfer business1. Define Your USP and Target Audience:Defining your Unique Selling Proposition (USP) and identifying your target audience are crucial initial steps before starting money remittance business. Your USP distinguishes your service from others, and understanding the specific demographic you aim to serve will shape your business strategy.2. Prepare All Required Documents and obtain Special Registration or LicensePrepare all necessary legal and regulatory compliance documents, including business registration documents, identification proofs, financial statements, and any other paperwork required by regulatory authorities in the countries where you intend to operate.Navigate the regulatory landscape by obtaining the necessary registrations or licenses to operate your remittance business. Compliance with local and international regulations is crucial to establishing the legitimacy and credibility of your operation. 3. Prepare All Processes, Including Compliance:Develop a robust framework that includes stringent anti-money laundering (AML) and Know Your Customer (KYC) procedures in alignment with regulatory guidelines. Establishing a solid foundation in compliance is essential for ensuring the security of transactions and building trust among users. Consider leveraging compliance-as-a-service, which provides remote and outsourced compliance services by professionals according to regulatory requirements.4. Open Correspondent Bank Accounts:The next step to start money remittance business is to ensure the smooth movement of funds by establishing correspondent bank accounts. Select reputable banking or financial services partners that align with your business goals. Transparent communication is key to building a strong financial relationship and ensuring the efficient flow of transactions.5. Set Your IT System or Core Banking Software:Invest in a secure, efficient IT system or core banking software like Macrobank. This system will be the backbone of your remittance operations, covering transaction processing, customer management, and data security. Additionally, consider implementing white-label mobile banking or web banking applications to deliver an exceptional experience to your customers.6. Make Partnerships with Financial Institutions:Forge strategic partnerships with financial institutions to expand your remittance network. Collaborate with banks, credit unions, remittance providers, or other financial entities to facilitate smoother transactions and extend the reach of your services.7. Make Required Integrations with Your Main Partners:Integrate your core banking system with key partners, including banks, payment gateways, or other financial service providers. Seamless integrations ensure interoperability and create a streamlined flow of funds between your remittance company and partnering entities. |
2024.05.10 07:20 unfufilledguy Can someone explain this network configuration?
Started a new gig after getting my CCNA but this simple thing is just confusing me. The engineers tried to explain why but I just can’t see why they did this.
We have two layer 3 switches both running EIGRP, one is the distribution switch and the other is the access switch. On the distribution switch there is a routed port-channel sub interface (po1.10) with IP 10.10.10.1/30 doing dot1q encapsulation for vlan 10 that connects to the access switch. Then on the access switch the connection is a port-channel L2 trunk (po1) with vlan 10 allowed and lastly there is Vlan 10 interface of 10.10.10.2/30 configured.
I’m having a hard time understanding why it’s setup this way, how frames are tagged with vlan headers and how things are being routed.
Let’s say vlan 15 is created on the access switch along with a SVI as the gateway, and a pc tries to send traffic to the Internet, does it hop to vlan 10 SVI and then add a 802.1q header, then when it gets to the distribution switch it strips vlan 10 header off and continues to the next hop? What’s the point of the vlan for a P2P network like this.
submitted by unfufilledguy to ccna [link] [comments]
We have two layer 3 switches both running EIGRP, one is the distribution switch and the other is the access switch. On the distribution switch there is a routed port-channel sub interface (po1.10) with IP 10.10.10.1/30 doing dot1q encapsulation for vlan 10 that connects to the access switch. Then on the access switch the connection is a port-channel L2 trunk (po1) with vlan 10 allowed and lastly there is Vlan 10 interface of 10.10.10.2/30 configured.
I’m having a hard time understanding why it’s setup this way, how frames are tagged with vlan headers and how things are being routed.
Let’s say vlan 15 is created on the access switch along with a SVI as the gateway, and a pc tries to send traffic to the Internet, does it hop to vlan 10 SVI and then add a 802.1q header, then when it gets to the distribution switch it strips vlan 10 header off and continues to the next hop? What’s the point of the vlan for a P2P network like this.
2024.05.10 02:28 toddwp Introduction
Fellow loyalists, please allow me to introduce myself,
My name is Todd. I'm 37 years old and live in Noosa on the Sunshine Coast. I've been waking up for about a decade now after learning about the debt slavery matrix through my foray into bitcoin in 2013 but am still only increasing in awareness of all that I don't know.
My great great... grandfather from my father's side was sent here for mugging a country estate in 1807, marrying a freeborn daughter from another convict sent here in 1797. After getting his freedom William became the first postmaster general at Richmond Post office as well as undertaker and blacksmith. My paternal grandfather fought in WW2 in South East Asia as artillery calculator and was wounded whilst on a transport boat by an aerial strafe in PNG having to swim several km to shore and hide in the bushes for a few days until US soldiers secured the beach.
For the last couple of years I have been attending a local community meetup that's progressed through the standard cycle of Commonlaw.earth, Commonwealth Custodians, and is now deep in the MyPlace brand. I've been attempting to bring forward information related to the UKOA and the important precedents that have been established but the usual ego trippers has taken it upon himself to censor me from the social channels as a Kingdom of Australia cultist that is disrupting the good efforts of Bergwerf's masterplan and the MyPlace community.
I have a B. Med.Sci , a Masters in Neuroscience, have a bunch of tools and can tackle most odd jobs at a handyman level. I have done an entire fit out on a commercial warehouse, building 8 artist studios and a 4 bedroom home on the mezzanine several years ago which though sturdy and comfortable lacked the polish of a professional.
I am currently engaged as an education consultant with the BSV Blockchain Assocation, a not for profit based out of Switzerland that stewards the original implementation of the Bitcoin Protocol. Our modus operandi is to set the protocol in stone so that it cannot be altered by the Mastercard and Bilderberg funded groups that pulled a coup on the BTC code repository so as to scuttle the protocol.
From my perspective this usurpation of the bitcoin protocol by these incumbents is an almost perfect analogue to the situation we find ourselves in with this foreign occupying administration.
A big part of my responsibility is to develop material which puts forward a case for digital transformations of an enterprise or even country utilising blockchain technology to set a new standard of integrity, accountability and transparency. I have many ideas for how we can utilise this technology to empower us as a people in our self determination. Our node software is currently being tested on an AWS set up, with three distributed nodes maintaining synchronisation whilst processing a sustained 1m transactions per second for several weeks now. This level of throughput creates an almost perfect economy of scale, wherein even at those levels, our transaction fees still stay around 1000th of a cent and trend cheaper over time. This massively threatens the money men and they've done their best to sway the public opinion regarding our cause in scaling the original set in stone protocol in much the same way as the occupier has done with the serfs of this country.
I lack the skills to actually code, but I have a solid understanding of distributed systems, networking protocols, and how to achieve data interoperability in a true p2p economy. I am especially interested in the synergy between IPv6 and the BSV blockchain and how this can enable value transfer at the edge of the network p2p without intermediaries. There are several designs that I am aware of that offer technical solutions to tokenising gold and silver down to the milligram, allowing for granular exchange of value with our constitutional currency. The caveat is it needs somewhere to be securely vaulted and for a meaningful solution to create accountability in whomsoever ends up as the custodian.
I have a range of other interests and skills which support me to serve in several capacities, having a strong command of written and spoken english, rapping and presenting as well as a solid foundation in health, history, economics, the scientific method, and more.
I suggested to MundiRex on youtube that a good complement to reddit would be setting up a mattermost instance where we can gather to chat freely on a server under our control. I am reticent to do it myself because I don't want to inherit any ambiguity around being the admin and elevating others to moderators etc. It should come under the proper line of authority.
I have been on reddit under another account for nearly 14 years. I understand this site well and have faced all manner of bots and agents during my more "internet activist" days. I was banned from conspiracy for a few years for challenging corrupt mods which themselves later got kicked out for their dodgy behaviour. Under that account I have several bots that downvote my comments and submissions instantly so please consider that there will be malicious tactics deployed against this subreddit through the usual Deny, Degrade, Disrupt, Deceive, Destroy tactics of our cyber adversaries.
I would love to connect with more people and contribute meaningfully to this effort. MundiRex if you have use for any of my skills please reach out and let me know how I may assist you in any way. I am eternally grateful for all you have done and provided for us to have a realm to stand righteous in under the blessing of Almighty God.
God Bless
submitted by toddwp to ukoa [link] [comments]
My name is Todd. I'm 37 years old and live in Noosa on the Sunshine Coast. I've been waking up for about a decade now after learning about the debt slavery matrix through my foray into bitcoin in 2013 but am still only increasing in awareness of all that I don't know.
My great great... grandfather from my father's side was sent here for mugging a country estate in 1807, marrying a freeborn daughter from another convict sent here in 1797. After getting his freedom William became the first postmaster general at Richmond Post office as well as undertaker and blacksmith. My paternal grandfather fought in WW2 in South East Asia as artillery calculator and was wounded whilst on a transport boat by an aerial strafe in PNG having to swim several km to shore and hide in the bushes for a few days until US soldiers secured the beach.
For the last couple of years I have been attending a local community meetup that's progressed through the standard cycle of Commonlaw.earth, Commonwealth Custodians, and is now deep in the MyPlace brand. I've been attempting to bring forward information related to the UKOA and the important precedents that have been established but the usual ego trippers has taken it upon himself to censor me from the social channels as a Kingdom of Australia cultist that is disrupting the good efforts of Bergwerf's masterplan and the MyPlace community.
I have a B. Med.Sci , a Masters in Neuroscience, have a bunch of tools and can tackle most odd jobs at a handyman level. I have done an entire fit out on a commercial warehouse, building 8 artist studios and a 4 bedroom home on the mezzanine several years ago which though sturdy and comfortable lacked the polish of a professional.
I am currently engaged as an education consultant with the BSV Blockchain Assocation, a not for profit based out of Switzerland that stewards the original implementation of the Bitcoin Protocol. Our modus operandi is to set the protocol in stone so that it cannot be altered by the Mastercard and Bilderberg funded groups that pulled a coup on the BTC code repository so as to scuttle the protocol.
From my perspective this usurpation of the bitcoin protocol by these incumbents is an almost perfect analogue to the situation we find ourselves in with this foreign occupying administration.
A big part of my responsibility is to develop material which puts forward a case for digital transformations of an enterprise or even country utilising blockchain technology to set a new standard of integrity, accountability and transparency. I have many ideas for how we can utilise this technology to empower us as a people in our self determination. Our node software is currently being tested on an AWS set up, with three distributed nodes maintaining synchronisation whilst processing a sustained 1m transactions per second for several weeks now. This level of throughput creates an almost perfect economy of scale, wherein even at those levels, our transaction fees still stay around 1000th of a cent and trend cheaper over time. This massively threatens the money men and they've done their best to sway the public opinion regarding our cause in scaling the original set in stone protocol in much the same way as the occupier has done with the serfs of this country.
I lack the skills to actually code, but I have a solid understanding of distributed systems, networking protocols, and how to achieve data interoperability in a true p2p economy. I am especially interested in the synergy between IPv6 and the BSV blockchain and how this can enable value transfer at the edge of the network p2p without intermediaries. There are several designs that I am aware of that offer technical solutions to tokenising gold and silver down to the milligram, allowing for granular exchange of value with our constitutional currency. The caveat is it needs somewhere to be securely vaulted and for a meaningful solution to create accountability in whomsoever ends up as the custodian.
I have a range of other interests and skills which support me to serve in several capacities, having a strong command of written and spoken english, rapping and presenting as well as a solid foundation in health, history, economics, the scientific method, and more.
I suggested to MundiRex on youtube that a good complement to reddit would be setting up a mattermost instance where we can gather to chat freely on a server under our control. I am reticent to do it myself because I don't want to inherit any ambiguity around being the admin and elevating others to moderators etc. It should come under the proper line of authority.
I have been on reddit under another account for nearly 14 years. I understand this site well and have faced all manner of bots and agents during my more "internet activist" days. I was banned from conspiracy for a few years for challenging corrupt mods which themselves later got kicked out for their dodgy behaviour. Under that account I have several bots that downvote my comments and submissions instantly so please consider that there will be malicious tactics deployed against this subreddit through the usual Deny, Degrade, Disrupt, Deceive, Destroy tactics of our cyber adversaries.
I would love to connect with more people and contribute meaningfully to this effort. MundiRex if you have use for any of my skills please reach out and let me know how I may assist you in any way. I am eternally grateful for all you have done and provided for us to have a realm to stand righteous in under the blessing of Almighty God.
God Bless
2024.05.07 11:24 Purple_Intention_206 Things to Keep In Mind While You Build Decentralized Exchange in 2024
 | submitted by Purple_Intention_206 to u/Purple_Intention_206 [link] [comments] https://preview.redd.it/8b7ahh643zyc1.png?width=764&format=png&auto=webp&s=4014b3f455322193c89a114aefed5cf502d72153 Undoubtedly, Decentralized Exchanges, or DEXs, are currently ruling the crypto space with their top-notch features and low gas fees. Getting started with decentralized exchange development is a dream for many entrepreneurs who want to venture into the crypto space. After experiencing the success of DEX platforms, most entrepreneurs are continuously facing some queries. One of the most common queries amongst them is what you need to consider while building a decentralized crypto exchange platform. If this query is popping in your head too, you’ve landed in the right place. In this blog, we’ll be discussing the key essentials that you need to consider while building a DEX platform. But, before that, let’s throw light on what DEXs are! What is a decentralized exchange?Decentralized exchange is a crypto exchange platform that allows users to conduct transactions directly without the need for intermediaries. These vary from the traditional centralized exchanges, where transactions occur over the platform. On the other hand, DEXs leverage blockchain technology, smart contracts, and even P2P trading systems, which provide users with greater control, anonymity, security, and transparency over their digital assets and currencies.Key Factors to Consider While Developing a Decentralised ExchangeWhile building a decentralized exchange in 2024, there are various factors that you need to consider to ensure its success, such as:
Wrapping UpIn 2024, the decentralized exchange development industry will witness phenomenal growth. So, if you’re willing to venture into the space in a seamless way, get in touch with the experts at Coin Developer India.It is a leading decentralized exchange development company in the field. They specialize in crafting top-notch DEX platforms on various blockchain networks, including Ethereum, Polygon, BSC, and more. Boasting a team of skilled blockchain developers, they can help you build a DEX to the highest standards. So, reach out to them today! Want to develop defi exchange? Call/Whatsapp: +91 7014607737 |
2024.05.05 18:51 enferlady New servers in asia
Is there any new servers in the Asian channel? Most of the servers I find are well established and ruled by p2p people hogging all the titles. Is there a beginner friendly or new Asian server? I'm so tired of seeing the same person winning all the titles and leaving nothing for anyone else.
submitted by enferlady to kingschoice [link] [comments]
2024.05.05 15:59 Dmit_Kha Pixel buds pro for wide ears
Hello community. I am longtime pixel phones user, and I have a question about the Pixel Buds Pro. During the last 4-5 years I have been using the WF-XB700 from, because of their design. I have wide ear channel, so any other earbuds I tried had dropped out from my ears. I tried some another variants from galaxy buds, OPPO, different other brands - and I understood that I need or some xl-xxl sealings, or some special earbud form.
Does anyone has the same problem and could reccomend the Pixel Buds Pro for replacing my old Sony? Last week I broke their charging case.
Thank you!
submitted by Dmit_Kha to pixelbuds [link] [comments]
Does anyone has the same problem and could reccomend the Pixel Buds Pro for replacing my old Sony? Last week I broke their charging case.
Thank you!
2024.05.05 13:59 gulmo Setting up ae2 p2p for channels. Getting channels, but losing ability to see or interact with what's on the p2p
I am stuck and wanted to see if anyone had advice for me. I've never used applied energetics before, and I am trying to use p2p to give channels to my machines, which is working in terms of channels, but the act of using the p2p cuts off my ability to see or interact with anything on that line. I've been stuck with this problem for days and I feel really stupid I can't figure it out. Any suggestions from anyone? I can post pictures or a short video of what it looks like if anyone is interested.
submitted by gulmo to GTNH [link] [comments]
2024.05.03 09:02 Jarvis_mark01 Risks of P2P Cryptocurrency Trading: Insights from Hyberabad’s Cybercrime Division
In Hyderabad, a civil service aspirant ventured into peer-to-peer (P2P) cryptocurrency trading, hoping to earn commissions. However, this turned into a cautionary tale of cyber vulnerability.
submitted by Jarvis_mark01 to BitcoinIndia [link] [comments]
P2P Trading and Cybercrime
P2P trading allows direct exchange of digital assets, often in online environments like Telegram channels. Cybercriminals exploit this to launder illicit gains, targeting traders with attractive commissions. Traders, unaware of fund origins due to lack of Know Your Customer (KYC) verification, can become unwittingly involved in criminal activities.Risks and Consequences
Authorities tracing financial transactions can inadvertently freeze a trader’s bank account. Traders might be forced to reimburse victims, losing their funds while fraudsters escape with laundered money.Advice from Cyberabad's Cybercrime Division
DCP K Shilpavalli advises caution, warning against P2P crypto trading with anonymous online entities. She stresses the importance of verifying KYC before trading and encourages anyone with cyber-related concerns to contact the helpline at 1930.2024.05.03 00:25 cyberbub101 F1TV - 2024 Formula 1 Round 06 - Miami Grand Prix Weekend (F1TV Live + International Feed) [1080p50 H264 AAC] (File download + magnet link)
✔️ Free Practice (✔️ International Feed)
✔️ Sprint Qualifying (✔️ International Feed)
✔️ Sprint Race (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Qualifying (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Race (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Drivers Press Conference
✔️ Team Representatives Press Conferences
✔️ Post-Sprint Press Conferences
✔️ Post-Qualifying Press Conferences
✔️ Post-Race Press Conferences
✔️ Free Practice Highlights
✔️ Sprint Qualifying Highlights
✔️ Sprint Highlights
✔️ Qualifying Highlights
✔️ Race Highlights
✔️ Weekend Warmup
✔️ Tech Talk
✔️ Race In 30
✔️ Say What?
✔️ Top 10 Onboards
✔️ Jolyon Palmer's Analysis
submitted by cyberbub101 to MotorsportsReplays [link] [comments]
✔️ Sprint Qualifying (✔️ International Feed)
✔️ Sprint Race (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Qualifying (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Race (✔️ International Feed) (✔️ Pre-Show) (✔️ Post-Show)
✔️ Drivers Press Conference
✔️ Team Representatives Press Conferences
✔️ Post-Sprint Press Conferences
✔️ Post-Qualifying Press Conferences
✔️ Post-Race Press Conferences
✔️ Free Practice Highlights
✔️ Sprint Qualifying Highlights
✔️ Sprint Highlights
✔️ Qualifying Highlights
✔️ Race Highlights
✔️ Weekend Warmup
✔️ Tech Talk
✔️ Race In 30
✔️ Say What?
✔️ Top 10 Onboards
✔️ Jolyon Palmer's Analysis
Format : Matroska Format version : Version 4 Overall bit rate : 6 195 kb/s Writing application : Lavf58.20.100 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : Main@L4.2 Bit rate mode : Constant Nominal bit rate : 6 000 kb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 50.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.058 Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : A_AAC-2 Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Comment : EnglishStream + Download:
Event Directory: https://ouo.io/1UevMFR Password: qrq2NAM_dtj8Magnet link (P2P):
magnet:?xt=urn:btih:fd8adec967c1a4493bf8ddbc1a33975ab0db2c7b&dn=F1%202024%20-%20R06%20United%20 States&tr=udp%3A%2F%2Fopentracker.i2p.rocks%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.cyberia.is%3A6969%2Fann ounce&tr=udp%3A%2F%2Fopen.stealth.si%3A80%2Fannounce&tr=udp%3A%2F%2Fipv4.tracker.harry.lu%3A80%2Fannounce&tr =udp%3A%2F%2Fzecircle.xyz%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Fop entor.org%3A2710&tr=udp%3A%2F%2Ftracker.ccc.de%3A80&tr=udp%3A%2F%2Ftracker.blackunicorn.xyz%3A6969&tr=udp%3A %2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Ftrac ker.opentrackr.org%3A1337%2Fannounce magnet:?xt=urn:btih:fd8adec967c1a4493bf8ddbc1a33975ab0db2c7b&dn=F1%202024%20-%20R06%20United%20 States&tr=udp%3A%2F%2Fopentracker.i2p.rocks%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.cyberia.is%3A6969%2Fann ounce&tr=udp%3A%2F%2Fopen.stealth.si%3A80%2Fannounce&tr=udp%3A%2F%2Fipv4.tracker.harry.lu%3A80%2Fannounce&tr =udp%3A%2F%2Fzecircle.xyz%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Fop entor.org%3A2710&tr=udp%3A%2F%2Ftracker.ccc.de%3A80&tr=udp%3A%2F%2Ftracker.blackunicorn.xyz%3A6969&tr=udp%3A %2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Ftrac ker.opentrackr.org%3A1337%2Fannounceor:
https://tormag.ezpz.work/anpsmkz2kx
2024.05.01 22:41 Fuzzy_Whereas_5001 I am looking to see if there is a mod/addon/something that can add the better p2p advanced memory card back into ATM9. I am missing this thing and to be perfectly honest I have started to use the clipboard from create to keep track of my channel usage/p2p connections. Is there anything like this mod
 | submitted by Fuzzy_Whereas_5001 to allthemods [link] [comments] |
2024.04.30 17:12 djminger007 RGB++ Bitcoin Tweet
 | A rather long epic tweet translated into English; submitted by djminger007 to NervosNetwork [link] [comments] https://preview.redd.it/kol78o6numxc1.png?width=750&format=png&auto=webp&s=7e0176516c24a269ef0ebe7f7fc7ead9e12cbb03 https://twitter.com/tmel0211/status/1785196853493182865?t=QxLqGbusy47LhEbhZxgXWA&s=19 Recently, the BTC derivatives market seems to be in a dilemma: 1) The expected big turnaround after BTC halving has not yet arrived; 2) The wealth creation effect after the launch of Runes protocol is not as expected; 3) The BTC layer2 focus project Merlin is temporarily silent after TGE. However, while they are all waiting to "let the bullets fly", I am more bullish @NervosNetwork . Why? Next, let me talk about my opinion: In my opinion, there are currently two major problems in the BTC derivative ecosystem market:
The current BTC ecosystem must deliver results in solving the liquidity problem of layer 1 derivative assets. Therefore, the Bitcoin derivatives market urgently needs to develop a closed-loop layer 2 solution that can be quickly formed in terms of technical architecture, market operations, and ecological implementation. The implementation of native RGB protocol and Lightning Network is too slow, and many EVM-Compatible protocol frameworks are still under construction. In comparison, only CKB public chain, as a paradigm of UTXO isomorphic binding chain, is gradually "accelerating" the implementation of the market's imagination of BTC layer2: RGB++, UTXO Stack, Lightning Network, DOB assets, full-chain games and other landing ecosystems are emerging one by one. In the short term, the CKB public chain can provide a quick “training exercise” for the BTC layer2 industry, allowing everyone to see that BTC derivative assets on the first layer can be expanded and circulated in the Turing-complete environment of the second layer; in the long term, CKB may be able to rely on its inherent technical advantages of “isomorphic binding” to establish a UTXO-structured layer2 mainstream unified market for the BTC layer2 market. The fundamental reason why CKB public chain can do this is that the UTXO Cell model of the CKB chain itself can include tokens, JavaScript codes, JSON strings, smart contracts and a complete Bitcoin UTXO state. Therefore, the CKB public chain can be regarded as a complete off-chain state machine of the BTC mainnet. It can synchronously store all states that occur on the BTC mainnet, which is equivalent to an extended DA layer of the BTC mainnet. It runs all calculations based on its Turing completeness, which is equivalent to a high-performance VM execution layer. The isomorphic binding characteristics of its UTXO structure provide secure interoperability for BTC. In simple terms, if we assume that the BTC mainnet can only do asset settlement, CKB has taken care of the extended functionality such as the DA layer, execution layer, and interoperability. It is precisely because of this foundation that CKB has achieved some things that are difficult to implement on the BTC original chain, such as RGB and Lightning Network. Taking RGB as an example, its complete implementation requires some off-chain clients to store part of the "state" respectively, and then send a Commitment commitment (a Hash calculated by hashing the original state data) to the main network through a one-time sealing technology. The commitment contains the spending conditions of UTXO, cannot be tampered with, and can only be triggered by another matching commitment to "unlock". If Alice wants to send BTC assets to Bob through the RGB protocol, Alice initiates a commitment agreement that Bob can unlock the UTXO for spending. After receiving the commitment, the BTC full node will wait for another corresponding commitment to be unlocked. When the two commitments match, a UTXO spending (settlement) of the main chain is realized. Therefore, for the RGB client verification system, the key lies in the fact that independent P2P individuals such as Alice and Bob must each maintain a "state copy" and prove to the main network online that they legally own a certain state. The asset division is completed by matching the old commitments and updating the status of the new commitments. The problem is that in order for these individuals to have this kind of collaboration ability, a very complete "infrastructure" is usually required. The crux of the RGB protocol network's inability to be implemented on a large scale at this stage is that it is too difficult to build this infrastructure to uniformly manage the status, requests, and communications of off-chain clients. The CKB public chain itself has the ability to store DA states and has the interoperability of isomorphic binding. If this difficult infrastructure project is replaced by the existing CKB chain, wouldn’t the problem of RGB client verification be solved? That’s right, this is the fundamental reason why RGB++ came into being. Following this line of thought, the payment network of the state channel model, the Lightning Network, can also be implemented on the CKB public chain. After all, the crux of the Lightning Network is also the problem of interactive state management between the decentralized Lightning Network nodes. Imagine that if the originally decentralized and complex off-chain operation "black box" can be efficiently implemented on an existing public chain, the landing and application process will naturally be faster. For example, state channel cycle management, UTXO account and settlement, on-chain state storage, P2P communication simplification, etc. Taking the issuance of Inscription assets as an example, the inscription assets originally issued on the BTC L1 mainnet fell into an extremely high-cost turnover and low circulation state after the MINT under the Fomo trend. How can these assets be efficiently circulated with the help of the CKB public chain?
How to do it? Because CKB's Cell state has global management capabilities, if there is a conflict in the state of different Cells, such as two usage commitments with conflicting states, CKB will reject the issuance of one of the Cell commitments to protect the security of asset state updates. In essence, this is a reflection of the strong programmability of the CKB public chain. It should be noted that Ethereum's layer 2 solution Plasma cannot achieve similar Turing-complete expansion. Therefore, if I want to accelerate the implementation of BTC layer2, I will vote for the camp representing UTXO isomorphic binding. Although the CKB public chain is a successful UTXO paradigm BTC layer2, how can it represent the mainstream camp alone? Therefore, CKB launched the UTXO Stack to expand the scale of its camp. This situation is like when Vitalik said that ZK-Rollup is the final outcome and everyone rushed to the ZK field to build layer2. If Satoshi Nakamoto jumped out and said that UTXO isomorphic binding is the orthodoxy of BTC Layer2, it is estimated that UTXO Stack will also become the basic framework for the rapid construction and deployment of layer2 in the ecosystem. The implementation of the UTXO Stack strategy is very much like a strategic upgrade of OP Stack to OP-Rollup, which will soon bring the layer2 paradigm of the UTXO structure into more mainstream vision. Above In short, the recent coldness of the secondary market will bring some pressure to the builders of the primary market. Previously, the chaos of the BTC layer2 market was also regarded as prosperity, but after calming down, the lack of standards, norms, mainstream narratives, and core problem solutions (liquidity) of BTC layer2 will become a difficult problem that must be overcome. Therefore, the downturn of Runes has undoubtedly given the UTXO isomorphic binding camp represented by the CKB public chain a "send east wind" moment. Note: This article is purely from the perspective of technical logic, and is a call for the UTXO isomorphism binding to BTC layer2 represented by the CKB public chain. It is not intended as a reference for secondary market investment advice. If you want to have a more systematic and comprehensive understanding of CKB, RGB++, isomorphic binding, and UTXO Stack, you can subscribe to web3Caff’s research report: |
2024.04.30 05:49 ntsd I made a WebRTC file-sharing web without the signaling server
WebRTC is a client-side secure P2P file-sharing using WebRTC.
submitted by ntsd to WebRTC [link] [comments]
Features
- Send multiple files in parallel.
- Generate SDP connection for WebRTC data channel.
- No server side (only use public STUN servers for ICE candidates).
- PGP Encryption. (The is used against MITM over DTLS)
- Responsive UI.
- Open-source license.
- QR Scan for SDP trade.
- Paste from the clipboard.
- short SDP by sdp-compact.
2024.04.29 18:54 -nervos- A Guide to Bitcoin L2's
 | This year CKB has been on fire as innovators find ways to use CKB as a Bitcoin Layer 2! submitted by -nervos- to NervosNetwork [link] [comments] Check out the first instalment of "The Ultimate Guide to Bitcoin Layer 2's", examining Liquid BTC, Rootstock and Stacks & the original RGB, read below to understand more. https://www.nervos.org/knowledge-base/ultimate_guide_bitcoin_layer_two_part_1 https://preview.redd.it/9ldzglz47gxc1.png?width=1920&format=png&auto=webp&s=a6d125963420cb60cc5adfda44c6d8a53aa88096 The Ultimate Guide to Bitcoin Layer 2s: From Liquid, Rootstock, and Stacks to RGB (Part 1) With the rise of Ordinal Theory and inscriptions having finally shattered the image of a conservative chain reserved only for payments, Bitcoin is now undergoing an unprecedented renaissance. The arrival of ordinals and inscriptions on Bitcoin not only triggered a new wave of experimentation with Bitcoin-native digital artifacts, it also sparked the crypto community’s interest in the potential of Layer 2 protocols built on top of it. While the Lightning Network has been experiencing growth since its inception, more recently, protocols like Stacks and Rootstock have gained significant traction, both in the value of their respective tokens and in the on-chain usage and mindshare occupied within the Bitcoin community. Moreover, many innovative Layer 2 solutions are currently being ideated and developed, including drivechains, spiderchains, RGB, zk-rollups, BitVM, ARK, and RGB++ built on Nervos CKB. This comprehensive guide to Bitcoin Layer 2s consists of two parts. Part 1 covers the three oldest and most popular Bitcoin Layer 2s (excluding the Lightning Network, which you learn more about in this article) in depth and introduces the reader to the still-in-development RGB protocol. The analysis of the first three protocols should give the reader a good general sense of the most common Bitcoin Layer 2 architectures. Before we dive into the architectures of the specific solutions, it’s first important to define Layer 2 networks within the context of Bitcoin. What are Bitcoin Layer 2s?The classification of Layer 1 and Layer 2 systems is a legitimate subject of controversy within the crypto community, with different projects and factions of the industry having differing views.Generally speaking, Layer 1 chains are sovereign blockchains with their own consensus mechanisms and security budgets, that can function independently without relying on any other chain for consensus, data availability, or execution. On the other hand, there is no firm consensus on the definition of Layer 2 protocols, as various pundits draw the line at different points. https://preview.redd.it/5ok22yj87gxc1.png?width=1920&format=png&auto=webp&s=3104f9207d3412916ad78869b693181fdbcae932 For example, the Ethereum Foundation defines a Layer 2 as a "separate blockchain that extends Ethereum and inherits the security guarantees of Ethereum." This means that any chain or protocol that doesn't inherit another chain's security can't be classified as Layer 2 in the eyes of the Ethereum Foundation. Under this strict definition, widely accepted within the Ethereum community, only rollups are considered Layer 2s. Payment channels, state channels and sidechains are left out of the paradigm. Sidechains are sovereign blockchains linked to a Layer 1 blockchain via a two-way bridge) or “peg,” enabling seamless cross-chain asset transfers. This makes distinguishing between Layer 1 chains and sidechains difficult, especially considering their technical similarities. For this reason, sidechain projects largely differentiate themselves from Layer 1s in their branding and ecosystem development direction. Namely, sidechains typically aim to extend or scale an existing Layer 1 ecosystem instead of developing their own from scratch. On the Bitcoin side of things, the "Layer 2" category is quite malleable. Namely, the Lightning Network, Liquid, Rootstock, and Stacks all brand themselves as Bitcoin Layer 2s, even though they have vastly different architectures and security assumptions. According to the Ethereum community’s accepted definition, only the Lightning Network (and arguably Stacks post the Nakamoto upgrade) meet the "Layer 2" criteria. One conceivable explanation for this disparity in viewpoints can be found in the Ethereum community’s conviction that a user must be able to withdraw Layer 2 assets solely through a Layer 1 transaction. In their view, if the users can't do this, and must rely on the honest or effective operation of third parties, the adjacent chain or protocol isn't a "Layer 2." However, this reasoning doesn't translate well in Bitcoin, where new assets are being defined and issued exclusively on Layer 2, with BTC being the primary (or only) Layer 1 asset considered. When it comes to withdrawing BTC from a Layer 2, only the Lightning Network fits this bill because Bitcoin lacks the ability to verify the complex conditions of these “Bitcoin Layer 2” systems. This means that a third party, typically a federation, has to manage the bridge and sign off on the transactions that move BTC from Layer 2 to Layer 1. Why Does Bitcoin Need Layer 2s?For what it's worth, Bitcoin doesn't necessarily need Layer 2 protocols to survive. However, Layer 2s benefit it greatly by scaling Bitcoin’s limited transaction throughput and extending its programmability.Bitcoin has been intentionally built to be minimal, slow, and resistant to change. Its design philosophy prioritizes security and decentralization over scalability, and simplicity over architectural complexity. Its conservative architecture makes it analogous to FedWire as a settlement layer or TCP/IP as the Internet's underlying communications protocol: higher-level layers are built on top of these, adding more functionalities and performance, but the base infrastructure remains simple and robust. https://preview.redd.it/gmv1rqpa7gxc1.png?width=1920&format=png&auto=webp&s=841f54beb3b67316c6e1a17b2f4d80a2443740d0 Bitcoin has a block time) of 10 minutes and a throughput of around seven transactions per second. Improving the speed and throughput on Layer 1 would translate into increased hardware requirements for running full Bitcoin nodes), hurting the network's decentralization, security, and, consequently, censorship resistance—the whole point of blockchains. At the same time, Bitcoin's base layer programmability, speed, and throughput are far from enough to serve the world's needs, which produces the need for higher-level layers. The goal of these systems is to increase Bitcoin’s throughput by orders of magnitude and support more sophisticated applications that require fully expressive smart contracts, greater speed, or better privacy—all without changing the Bitcoin base layer. This way, Bitcoin can have its cake and eat it too, i.e., it can scale and support more sophisticated dApps without compromising its core values. Overview of The Most Popular Bitcoin Layer 2sTo this point, following the recent rise in popularity of digital artifacts or NFTs and BRC20 tokens on Bitcoin in the form of ordinals and inscriptions, the primary focus of enriching Bitcoin seems to have shifted from scalability or throughput-focused Layer 2s like the Lightning Network and Liquid to smart contract-enabled protocols like Rootstock, Stacks, and RGB, as well as more novel solutions like BitVM and the RGB++ protocol built on CKB.The Lightning Network is a payment channel network that allows users to route payments across payment channels and make nearly instantaneous Bitcoin transactions with negligible fees. Because much has already been written about how the Lightning Network works, we won’t dwell too much on it beyond highlighting that it’s the oldest and most widely adopted Bitcoin Layer 2, with over 5,000 BTC locked inside it. https://preview.redd.it/9lg2wgyc7gxc1.png?width=1999&format=png&auto=webp&s=e228e35765bd0b65aa36ec23edbbff6b0aac1892 The total value locked of wrapped Bitcoin (wBTC). Source: DefiLlama. By comparison, over 154,000 wrapped Bitcoin (wBTC) are currently circulating on Ethereum, which goes on to show the enormous appetite for using BTC for more than just payments, as a productive asset that can be lent, borrowed, collateralized, used for market-making on AMMs, and so on. Liquid NetworkThe Liquid Network is a federated sidechain developed by Blockstream, a blockchain technology company led by co-founder Adam Back. Back is a notable cryptographer, cypherpunk, and inventor of Hashcash, an algorithm that inspired Bitcoin’s Proof-of-Work mining mechanism.In essence, Liquid is a sovereign, permissioned, and, therefore, centralized chain that extends Bitcoin by creating a smoother environment for transacting BTC. It has faster block times (one minute) and two-block settlement finality (block reorganizations are disallowed under its proof of authority consensus). Liquid also allows permissioned issuance of other digital assets, including stablecoins and tokenized securities. https://preview.redd.it/p3ywpmmf7gxc1.png?width=1453&format=png&auto=webp&s=4b66a45566ffb6929f092f1b0f13026f9bfc9766 In the Liquid Network, transactions and blocks are signed by a federation of blocksigners using a BFT consensus algorithm. In contrast, the “peg-out” transactions (BTC withdrawals to Layer 1) are signed by a federation of “watchmen”, essentially drawn from the same pool of about 65 globally distributed federation members, comprising crypto exchanges, financial institutions, and other Bitcoin-focused companies. The “peg-in” or bridging process of transferring BTC to Liquid involves sending it to a Liquid-generated Bitcoin federated address that’s managed by the consortium of functionaries. After the Layer 1 BTC has been transferred to the address, the users receive a synthetic BTC asset on Liquid backed by the real BTC on Layer 1, called Liquid Bitcoin (L-BTC). Because the manual peg-in process is somewhat burdensome, requiring considerable technical skills and running both a Bitcoin full node and a Liquid node, most users acquire their L-BTC via third parties. Unlike peg-ins, withdrawals can only be done by Liquid’s federation members. However, regular users can alternatively peg-out by swapping their L-BTC for BTC through third parties, including centralized exchanges or trustless P2P swaps. https://preview.redd.it/vvklm0yh7gxc1.png?width=1920&format=png&auto=webp&s=951277aa4d2f0d1e7c5b319c9f7f9934c2eb3fd8 Finally, it’s important to note that Liquid doesn’t meet the stricter Ethereum definition for Layer 2, as it neither inherits Bitcoin’s security guarantees nor allows permissionless BTC withdrawals solely via a Layer 1 transaction. RootstockIn many ways the opposite of Liquid, Rootstock is significantly closer to the strict definition for Layer 2, meeting one of the two key criteria. It's an EVM-compatible smart contract-enabled sidechain that partially inherits Bitcoin's security via merged mining and links to it via a federated two-way peg. https://preview.redd.it/7fezeusk7gxc1.png?width=1920&format=png&auto=webp&s=16ba67f4c7bda9ebd81c3c2dca339c00a59f6a97 Rootstock goes beyond Liquid in that it doesn't seek only to scale Bitcoin's transaction throughput, but also to extend its programmability. With its Turing-complete smart contracts, Rootstock allows for the use of synthetic Bitcoin (RBTC) across various DeFi applications. Its engine is powered by the Rootstock Virtual Machine (RVM), a forked version of the Ethereum Virtual Machine (EVM), which is fully compatible with Ethereum smart contracts and tooling. This means Ethereum developers can conveniently deploy their dApps on Rootstock with little to no modifications. However, unlike Liquid, which is a centralized sidechain secured by a federation of pre-selected entities, Rootstock borrows Bitcoin's security via merge mining—a technique allowing Bitcoin miners to concurrently mine Rootstock blocks with nearly zero marginal cost (all that is required is a Rootstock node). This method benefits Bitcoin miners by providing them an additional revenue stream from the Layer 2 transactions (thus also increasing Bitcoin's security budget) and helps Rootstock essentially "free ride" on the back of Bitcoin's exceptional security. As things currently stand, Rootstock is backed by roughly 40% of Bitcoin's hash rate, making it somewhat protected from potential 51% attacks. However, this security largely depends on the Bitcoin miners' self-interest in securing additional revenues from Rootstock transaction fees. If the activity on the sidechain were to drop, the incentives for merge-mining would diminish, leaving Rootstock vulnerable to relatively low-cost 51% attacks and MEV or double-spend-motivated chain reorganizations. While Rootstock has implemented two protection mechanisms to mitigate these risks, “signed notifications” and “transparent double-spend trails”, its security is still far from that of Bitcoin. Moreover, mining a smart contract-enabled chain is not the same as mining Bitcoin. Smart contract chains use substantial computational resources, and once there is substantial smart contract activity on Layer 2, merge-mining could become much less attractive to Bitcoin miners. To this point, expecting or relying on Bitcoin miners to merge mine smart contract layers may not be a good long-term idea, as they can opt-out at any time, a potential risk of centralization in the block production of the merge mined chain. Rootstock's solution for a two-way peg is similar to Liquid’s. Part of the two-way peg system requires trust in a set of semi-trusted third parties, collectively called the Federation. Fully trust-minimized, third-party-free pegs can only be made between two Turing-complete smart contract platforms. However, since Bitcoin isn’t Turing-complete and doesn’t support native opcodes to validate external SPV proofs, any linked two-way pegs must be trusted and somewhat centralized. The bridging process is similar to that on Liquid: BTC is locked on Bitcoin and an equivalent amount of RBTC is minted on Rootstock. The locked Layer 1 BTC is controlled by the Federation, which has the ability to release the funds when users initiate a withdrawal. While this process isn’t necessarily trust-minimized and decentralized, it is automated, meaning withdrawals don’t require actual human intervention. Finally, it’s worth highlighting that since Rootstock doesn’t have its own separate security budget, it doesn’t (need to) have its own native token. Instead, RBTC is the native currency used to pay for transaction fees on Rootstock. StacksRight off the bat, it’s essential to know that as of Bitcoin’s second halving, Stacks will undergo a monumental upgrade, called the Nakamoto Release. Moving forward, we’ll only explain how Stacks will function after the Nakamoto release and not how it did prior.To this point, Stacks is a different type of smart contract layer compared to a sidechain, with a deeper, ongoing relationship with Bitcoin. It aims to give dApp users the best of both worlds: fast transactions with Bitcoin finality. Unlike Bitcoin’s 10-minute block time, Stacks blocks are produced every 5 seconds, with all Layer 2 transactions eventually settling on Bitcoin and benefiting from its exceptional security. Stacks isn’t EVM-compatible; instead, its smart contracts are written in its own proprietary language called Clarity. Unlike Liquid and Rootstock, Stacks has its own native asset, STX, which is central to its novel consensus mechanism dubbed Proof-of-Transfer (PoX). In PoX, Stacks miners spend (already mined) BTC and are rewarded in STX, similar to how Bitcoin miners spend electricity and are rewarded BTC in Proof-of-Work (PoW). Like in PoW, PoX uses a Nakamoto-style single-leader election, where PoX miners bid by spending BTC, and they have a bid-weighted random probability of becoming a leader. In this context, a leader is a miner who’s been selected to mine a Stacks block. https://preview.redd.it/jtg6er6n7gxc1.png?width=1345&format=png&auto=webp&s=c6ee69f018b4756921f0779e27577da32ac14ac1 A graphic showcasing Proof-of-Transfer (PoX). Source: docs.stacks.co The unique feature of Stacks’ consensus mechanism is how deeply it’s intertwined with the Bitcoin blockchain. Namely, using an open bidding process on Bitcoin, a group of Stacks miners is elected to mine Stacks blocks until the next Bitcoin block (at a 10-minute average Bitcoin block time, this is approximately 120 Stacks blocks). Once the miner set is elected, these miners use a BFT-style quorum signing, weighted by their BTC bids, to mine Stacks blocks every 5 seconds until the next Bitcoin block, for which they’re rewarded STX tokens. By leveraging BTC for bidding and Layer 2 miner selection, Stacks’ PoX consensus mechanism reuses the work already done by Bitcoin miners without consuming any significant amount of additional electricity. https://preview.redd.it/j2uzug7p7gxc1.png?width=1758&format=png&auto=webp&s=2f0fd5980d712d526146dd4a8b87a672d773d858 This means that post-Nakamoto upgrade, Stacks has two types of blocks at the Layer 2 level: (a) fast blocks, produced by Stacks miners every 5 seconds via a BFT-style quorum signing, and (b) settlement blocks (produced at every Bitcoin block) that don’t contain any new Layer 2 transactions but only settle the recent sequence of fast blocks (from the Stacks chain) on the Bitcoin chain. The fast blocks are produced as a single sequence between two settlement blocks and don’t fork. According to the Stacks protocol’s forking rules, forks are allowed only on settlement blocks and only at a depth of 1 to 6 Bitcoin confirmations. Stacks settlement blocks depth 7 to the latest finalized block (defined as a settlement block with 150 Bitcoin block confirmations) are “frozen,” meaning miners can fork them only through Stackers’ blessing to “unfreeze” a block. In PoX, Stackers are entities who lock or “stack” STX tokens and perform peg-out signing (explained below) and other consensus-critical tasks, including unfreezing blocks. Settlement blocks with over 150 Bitcoin block confirmations (about a day’s worth of blocks) are considered finalized and can never be forked. In simple terms, this means that most of Stacks’ history, or all blocks older than a day, follow Bitcoin finality and are secured by 100% of Bitcoin’s hash rate. To attack the Stacks history or alter a transaction more than about a day old, an attacker would have to do a deep reorganization of Bitcoin, which is extraordinarily difficult, if not impossible, considering Bitcoin’s current security budget and how decentralized its mining is. Effectively, the Stacks chain has two security budgets: one that includes the BTC spent by Stacks miners and the STX capital locked by Stackers (which secures only the blocks with less than 150 Bitcoin block confirmations), and secondly, Bitcoin’s entire security budget that secures Stacks’ more-than-a-day-old history. This mixed security mechanism makes most of the Stacks chain significantly more secure than Liquid or Rootstock. Similarly, the way Stacks’ two-way peg is designed offers much better security guarantees than those of its federated competitors. Because Stacks has its own native token, it can use clever incentives engineering to deliver a peg that's managed in a permissionless and decentralized way. Namely, the sBTC peg is maintained by the Stackers of the PoX consensus protocol, who lock STX as collateral for the right to sign peg-out transactions and earn BTC rewards. Unlike in federated models of Liquid and Rootstock, in Stacks, anyone can become a Stacker and sign off on peg-outs. The locked or staked STX serves as collateral at risk of slashing to disincentivize bad behavior. Additionally, BTC rewards serve as incentives for honest Stackers who only sign valid peg-outs, not malicious ones. RGBRGB (Really Good Bitcoin) is one of the most novel developments in Bitcoin. It represents a set of open-source protocols for scalable and private smart contracts on Bitcoin and the Lightning Network. \As a smart contracting extension to Bitcoin, RGB is quite different compared to other Bitcoin Layer 2 solutions and even non-Bitcoin smart contract platforms. Namely, it takes smart contracts execution and validation entirely off-chain, using Bitcoin only as a state commitment layer and Bitcoin script as an ownership control system. https://preview.redd.it/gfidjd1s7gxc1.png?width=1920&format=png&auto=webp&s=2beec75c1a2f621b8e6e643593b94d5adaa0693e The entire system is based on client-side validation and single-use seals. Client-side validation means that all RGB smart contracts and transactions are executed and validated by parties to the transactions (off-chain) without posting any data on Bitcoin. The single-use seals (inscribed over Bitcoin or Lightning Network transaction outputs) represent RGB’s security mechanism, allowing any party holding a smart contract’s history to verify the integrity of its execution by combining on-chain and off-chain data. https://preview.redd.it/jqk6tk3v7gxc1.png?width=1920&format=png&auto=webp&s=a5c21de68c8c57e330e271ae4624e6ac9951b1b8 Unlike other smart contract platforms, RGB separates the concepts of smart contract issuers, state owners, and state transitions. Namely, each RGB smart contract is represented by some genesis state created by the smart contract issuer and a directed acyclic graph (DAG) of state transitions kept as client-validated (entirely off-chain) data by RGB users. The state is _assigned _to a Bitcoin UTXO, which defines them as “single-use seals”. The party that can spend the corresponding UTXO is called the state _owner _(in the genesis state’s case, that’s the state issuer). The state owner can change the corresponding part of the smart contract state by creating a new state transition and committing it via a transaction that spends the output containing the previous state. In simpler terms, RGB defines smart contract ownership by binding/assigning state via single-use seals to Bitcoin transaction outputs (UTXO’s)—whoever controls the output owns the associated state. However, whereas the ownership defines _who _can change the state, the client-side validation rules define how the state may change. The validation rules are defined by an RGB Schema, a blueprint or standard for constructing RGB smart contracts similar in nature to the ERC standard for token contracts on Ethereum. The Schema defines everything from the types of metadata smart contracts can use to the types of state transitions, seal transitions, state and metadata semantics, etc. In other words, when issuers define their smart contracts, they must ensure they adhere to or “validate against” the particular RGB Schema; otherwise, wallets and exchanges won’t support them. This is because when wallets or exchanges get information about some asset (data and contract), they must validate it against a specific Schema and only accept the asset if it passes the validation against that Schema. The wallets or exchanges will leverage specialized Schema libraries, like “RGB fungible assets” or “RGB collectibles,” instead of a single complex RGB core library. Moving on, RGB operates in “shards,” where each contract has a separate state history and data that never intersects with the states of other smart contracts, allowing for another level of scalability. Importantly, RGB’s sharded nature doesn’t mean its contracts can’t interact. Much to the contrary, they can interoperate via the Bifrost protocol over the Lightning Network, enabling multiparty coordinated state changes that open the door to complex applications, including decentralized exchanges over the Lightning Network and money market protocols. In conclusion, RGB aims to bring smart contracting capabilities to Bitcoin that go far beyond what’s possible on Ethereum, providing more scalable, private, and arguably safer smart contract solutions. ConclusionIn this first part of our two-part series on Bitcoin Layer 2s, we explained how the term “Layer 2” is used differently in a Bitcoin context compared to Ethereum, covered the three oldest and most popular Bitcoin Layer 2 protocols, and provided a technical introduction to the most novel still-in-development Bitcoin Layer 2 solution, RGB.In Part 2, we’ll cover the expansive landscape of new Bitcoin Layer 2 innovations, including RGB++, which is being built on CKB! |
2024.04.29 14:31 cardano_content_bot Discover the details of the upcoming P2P upgrade and how you can participate in this clip from the Essential #Cardano360 show. 🗣️ Stakeholders, including SPOs and users, can provide feedback through various channels: 🤖 Discord: Visit the P2P mainnet or
 | submitted by cardano_content_bot to cardano [link] [comments] |
2024.04.29 10:28 djminger007 CKB: A new chapter in the programmability of bitcoin
This is a really good read I've picked up from Neon in Nervos Nation TG from a Chinese website and the browser has translated it, seems like a good translation from Brave!!! Please be aware there are a few images that cannot be transferred form this article, but if you're not caring about lines of code or any of the schematics, you can give this a good read regardless.
Bullish; Heres the link for those that might want to cross reference
https://mirror.xyz/0xB239e7668B6dAF0122166E2De879Da87FF47858C/hkXPFe0uBy2fQNIzjVrL0rMUONj2hTJklaN14Rbguuk
The programmable evolution and iteration of Bitcoin is the result of market governance in the Bitcoin community, not driven by the theory of Holder of BTC, Builder of block space, etc.
At present, by enhancing the programmability of Bitcoin and increasing the utilization rate of the block space of the main network of Bitcoin, it has become a new design space for the consensus of the Bitcoin community.
Unlike Etai and other high-performance public chains, in order to ensure the simplicity and light quantification of UTXO episodes, the design space for the programmability of bitcoins is highly restricted, and the basic constraints are how to use scripts and OP Code to operate UTXO.
The classic Bitcoin programmable program has a state channel （ Lightning Network ）, customer end verification （RGB）, side chain （Liquid Network, Stacks, RootSock, etc. ）, CounterParty, Omni Layer Asser, TaproC, etc. Emerging bitcoin programmability programs since 2023 include Ordinals, BRC20, Runes, Atomicals, Stamps, etc.
After the end of the second wave of inscriptions, a new generation of bitcoin programmability programs and so on emerged, such as CKB's UTXO co-construct binding program, EVM compatible bitcoin L2 program, DriveChain program, etc.
Compared with the EVM compatible bitcoin L2 scheme, CKB（Common Knowledge Base） The Bitcoin Programmability Program is a native, safe, and non-introducing social trust hypothesis solution in the Bitcoin Programmability Modern Design Space. Compared with the DriveChain plan, it does not require any change in the level of the Bitcoin agreement.
In the foreseeable future, the programmable growth curve of Bitcoin will go through an accelerated growth stage, and the assets, users, and applications of Bitcoin ecology will usher in a massive outbreak of martial arts，The UTXO Stack of the CKB ecology will provide new Bitcoin developers with the ability to build protocols using modular stacks. In addition, CKB is exploring the integration of the lightning network with UTXO Stack, using the original programmability of Bitcoin to achieve interoperability between the new agreements.
In the process of coordinated evolution of Bitcoin Maxi and expansionists, from whether the Bitcoin main network supports Turing’s complete struggle to the dispute between the isolation witness program and the large block expansion plan, Bitcoin is constantly split. This is not only creating new encryption projects and encryption community consensus, but also strengthening and consolidating Bitcoin's own community consensus, which is a process of completing self-identification while others are institutionalized.
Due to the mysterious disappearance of Satoshi Zhong, Bitcoin community governance does not exist in the governance structure of the “ enlightened monarchy ” like Taifang, but is a balanced governance model in open games by miners, developers, communities and markets. This gives Bitcoin a community consensus that once formed and is extremely stable.
The characteristics of the current Bitcoin community consensus are: consensus is not command and control, trust minimization, decentralization, anti-censorship, anonymity, open source, open collaboration, licensing exemption, legal neutrality, homogenization, forward compatibility, resources Use minimization, verification > calculation, convergence, transaction volatility、Resist DoS attacks, avoid scramble entry, robustness, consistent incentives, curing, consensus that should not be tampered with, conflicting principles, collaborative advancement, etc. [1]
The current form of the Bitcoin main network can be regarded as an example of the consensus characteristics of the above Bitcoin community. The programmable design space of Bitcoin is also defined by the consensus characteristics of the Bitcoin community.
Two typical examples are the two major upgrades to the Bitcoin main network since 2017, Segwit hard fork and Taproot soft fork.
In August 2017, Segwit bifurcated hard, adding 3M blocks outside the main block of 1M to save the signature （ Witness）, and setting the weight of the signature data as the main block when calculating the miner’s fee 1/4 to maintain consistency in the cost of spending a UTXO output and creating a UTXO output，Prevent the abuse of UTXO to zero to increase the expansion rate of UTXO sets.
In November 2021, Taproot's soft fork was introduced by introducing Schnorr's multiple signature program to save UTXO's verification time and block space occupied by multiple signatures.
UTXO（ The unspent transaction output ） is the basic data structure of the Bitcoin main network, which has atomic, non-homogeneous, and chain-coupled characteristics. Every transaction on the main net of Bitcoin consumes 1 UTXO as input, and creates an integer n new UTXO output. It is generally understood that UTXO can be regarded as a dollar, euro and other banknotes running on the chain. It can cost, change, split, combine, etc., but its minimum atomic unit is Satoshi（sats）. 1 UTXO represents the latest state at a particular time. UTXO episode, which represents the latest state of the Bitcoin main network at a certain time.
By maintaining the simplicity, light quantification, and easy verification of the Bitcoin UTXO episode, the state expansion rate of the Bitcoin main network has successfully stabilized at a level compatible with the hardware Moore law, thereby ensuring the participation of the entire Bitcoin network nodes And the robustness of transaction verification.
Correspondingly, the programmable design space of Bitcoin is also constrained by the consensus characteristics of the Bitcoin community. For example, in order to prevent potential security risks, Satoshi Nakamoto decided to remove the OP-CAT operation code in August 2010, which is the key logic for achieving programmability at the complete level of Bitcoin Turing.
Bitcoin's programmable realization path does not use the virtual machine （VM） scheme in the chain like Taifang and Solana, but chooses to use the script and operation code （OP Code） for UXTO, transaction Input field, output field and witness data （Witness）.
The main toolboxes for programmability of bitcoin are: multiple signatures, time locks, Hash locks, process control （OP_IF, OP_ELIF）. [2]
Under the classic design space, the programmability of bitcoin is very limited. It only supports a few verification procedures, but does not support chain storage and chain calculations, and chain storage and chain calculations are precisely to achieve Turing's complete level programmability. Core functional components.
Unlike the outside world's stereotype that the development of the Bitcoin main network is at a standstill, in the case of various consensus vectors limiting the design space, the development, deployment, adoption, and promotion of the new script and new operation code of the Bitcoin main network are always in progress Times，And at some point even triggered a fork war in the encrypted community （ such as Segwit hard fork ）.
Taking the Bitcoin main net script type with degree change as an example, we can clearly perceive the changes. We can divide the scripts used by the Bitcoin main network output type into three categories: original script pubkey, pubkeyhash, enhanced script multisig, scripthash, witness script witness_v0_keyhash, witness_v0_scripthash, witness_v1_taproot.
From the change trend chart of the entire historical output type of the Bitcoin main network, we observe a basic fact: the programmability enhancement of the Bitcoin main network is a long-term historical trend, enhancing the share of scripts in the original script, and witnessing the script being swallowed The share of the enhanced script. The Ordinals agreement based on Segweit's enhanced script and Taproot's witness script opened a wave of Bitcoin L1 asset issuance, which is both a continuation of the programmable historical trend of the Bitcoin main network and a new stage of programmability of the Bitcoin main network.
The Bitcoin main network operation code also has an evolutionary process similar to the Bitcoin main net script.
For example, the Ordinals agreement is to achieve its functional design by combining the Bitcoin main net script taproot script-path spend and operation code （OP_FALSE, OP_IF, OP_PUSH, OP_ENDIF）.
Before the official birth of the Ordinals agreement, the programmable classic plan of bitcoin mainly has the state channel （ Lightning Network ）, customer verification （RGB）, side chain （Liquid Network, Stacks, RootSock, etc.）, CounterParty, etc.
The Ordinals agreement sequences the smallest atomized unit of UXTO （Satoshi）, and then inserts the data content in the Witness field of UTXO, and is associated with a specific deafness after sequencing, and then the chain indexer is responsible for indexing and Perform programmable operations of these data states. This new bitcoin programmability paradigm is vividly likened to “ Golden Eagle ”.
The new paradigm of the Ordinals agreement has inspired a wider range of encrypted communities to use the Bitcoin main network block space to distribute, cast and trade NFT collections and MeMe-type Token（, which can be collectively referred to as the inscription ）. For the first time in life, you have your own Bitcoin address.
However, the programmability of the Ordinals agreement inherits the limited programmability of Bitcoin and only supports the three functional methods of Deploy, Mint and Transfer. This allows the Ordinals agreement and its followers BRC20, Runes, Atomicals, Stamps, etc. to apply only to the application scenes where assets are issued. Support for DeFi application scenes such as transactions and loans that require state calculation and state storage is relatively weak.
Liquidity is the source of vitality for assets. Due to the natural characteristics of the programmability agreement of the Ordinals type bitcoin, the reissue of the inscription assets and the provision of light liquidity affect the value of the entire life cycle of the inscription assets.
Moreover, the Ordinals and BRC20 agreements are also suspected of misusing the witness data space and objectively causing the explosion of the main network of Bitcoin.
As a reference system, the main sources of the Pacific Master Network Gas fee are DEX transaction Gas fee, L2 data availability fee, and stable currency transfer Gas fee. Compared with the Taifang main network, the income type of the Bitcoin main network is single, cyclical, and the volatility rate is large.
The programmability of the Bitcoin main network cannot yet meet the demand for the space supply side of the Bitcoin main network block. To achieve a stable and sustainable block space income state with the Pacific Master Network, the original DEX, stable currency and L2 of the Bitcoin ecology are required. The prerequisite for the realization of these agreements and applications is that Bitcoin programmable agreements need to provide Turing's complete programming capabilities.
Therefore, how to achieve the complete programmability of Bitcoin Turing in its original place, while constraining the negative impact on the size of the Bitcoin main network, has become a current manifestation of Bitcoin ecology.
BitVM uses a group of OP Code in Bitcoin to build and non-logical doors, and then builds other basic logical doors with non-logical doors. Eventually, these basic logical gate circuits construct a VM native to Bitcoin. This principle is somewhat similar to the array of the Qin king of the famous science fiction novel 《 Tripartite 》. There are specific scenes in the TV series of the same name adapted by Netflix. The paper of the BitVM program has been completely open source, and is highly expected by the encrypted community. However, its engineering implementation is very difficult. It is difficult to land in the short term when it encounters problems such as data management costs under the chain, the number of participants, challenges-response interactions, and the complexity of the Hash function.
The RGB protocol uses customer end verification and one-time sealing technology to achieve the complete programmability of Turing. The core design idea is to store the status and logic of the smart contract in the output of the bitcoin transaction （Transaction）On the implementation of the maintenance and data storage of the smart contract code under the chain，The main network of bitcoins serves as the commitment layer of the final state.
EVM compatible with Rollup L2 is a quick plan to rebuild Bitcoin L2 with a mature Rollup L2 stack. However, given that the Bitcoin main network is currently unable to support fraud certification/validity certification, Rollup L2 needs to introduce the social trust assumption （ over-sign ）.
DriveChain is a side chain expansion plan. The basic design idea is to use Bitcoin as the bottom layer of the block chain, and to create side chains by locking Bitcoin to achieve two-way interoperability between Bitcoin and side chains. The realization of the DriveChain project requires agreement-level changes to Bitcoin, which will deploy the BIP300 and BIP301 proposed by the development team to the main network.
The above Bitcoin programmability plan is either extremely difficult to land in the short term, or introduces too many social trust assumptions, or requires agreement-level changes to Bitcoin.
Original language of UXTO: tied to the same organization
RGB++ is a bitcoin L1 asset issuance agreement based on RGB design ideas. The project of RGB++ was realized, while inheriting the technical original words of CKB and RBG. It uses RGB's “ one-time seal ” and customer end verification technology, and at the same time tied up the UTXO（ expanded version of Cell） that maps Bitcoin UTXO to the CKB main network, and uses CKB and Bitcoin chains Script constraints to verify the accuracy of status calculations and the validity of ownership changes.
In other words, RGB++ uses Cell on the CKB chain to express the ownership relationship of RGB assets. It moves the asset data originally stored at the end of the RGB customer to the CKB chain and expresses it in the form of Cell. It establishes a mapping relationship with Bitcoin UTXO, allowing CKB to act as an open database and chain of RGB assets. Settlement layer, replacing RGB client，Achieve more reliable data hosting and RGB contract interaction.
Cell is the basic data storage unit of CKB and can contain various data types, such as CKBytes, tokens, TypeScript codes or sequencing data （ such as the JSON string ）. Each Cell contains a small program called Lock Script, which defines the owner of Cell. Lock Script not only supports the scripts of the Bitcoin main network, such as multiple signatures, Hash locks, time locks, etc., but also allows a Type Script to enforce specific rules to control its use. This allows developers to customize smart contracts according to different usages, such as issuing NFT, airdropping tokens, AMM Swap, etc.
The RGB protocol adds the root of the transaction under the chain to a UTXO'output by using the OP RETURN operating code, and uses UTXO as a container of status information. Then, RGB++ map this state information container constructed by RGB to Cell in CKB, keep the state information in Cell's type and data, and use this container UTXO as the Cell state owner.
As shown in the figure above, a complete RGB++ transaction life cycle is as follows：
To trust L1<>L2 interoperability: Leap
The tied tie of the same structure of RGB++ is a common logic for the realization of a common atom, which either occurs at the same time or flips at the same time without intermediate states. All RGB++ transactions will appear simultaneously on the BTC and CKB chains. The former is compatible with the transactions of the RGB agreement, while the latter replaces the process of customer end verification. The user only needs to check the relevant transactions on the CKB to verify whether the calculation of the status of the RGB++ transaction is correct. However, users may also use the transaction on the CKB chain as the verification basis, and use the local Tx map of UTXO to independently verify the RGB++ transaction. （Part of the functions such as transaction folding still need to rely on CKB block Hashi for anti-double flower verification ）
Therefore, the asset cross-chain between RGB++ and the CKB main network does not rely on the introduction of additional social trust assumptions, such as the relay layer of the cross-chain bridge, the centralized multi-sign vault of EVM compatible Rollup, etc. RGB++ Assets can be transferred from the Bitcoin main network to the CKB main network, or from the CKB main network to the Bitcoin main network. CKB calls this cross-chain workflow Leap.
RGB++ and CKB are loosely coupled. In addition to the assets supporting the Bitcoin L 1st floor （ are not limited to the original assets of the RGB++ agreement, including assets issued by Runes, Atomicals, Taproot Asset and other agreements ）Leap to CKB, RGB++The other support Leap to Cardan. At the same time, RGB++ also supports Bitcoin L2 assets Leap to Bitcoin main network.
Examples of extended functions and applications of RGB++
The RGB++ agreement originally supported the issuance of homogenized tokens and NFT.
The homogenized token standard of RGB++ is xUDT, and the NFT standard is Spore.
The xUDT standard supports a variety of homogenized tokens issuance methods, including but not limited to centralized distribution, airdrops, subscriptions, etc. The total amount of tokens can also be selected between the upper limit and the upper limit. For the tokens with a preset upper limit, a status sharing scheme can be used to verify whether the total number of each issuance is less than or equal to the preset upper limit.
Spore in the NFT standard will store all metadata on the chain, achieving 100% data availability security. Assets issued by the Spore Agreement DOB（Digital Object, digital object）, similar to Ordinals NFT, but with richer characteristics and play methods.
As a customer verification agreement, the RGB protocol naturally supports state channels and lightning networks, but is limited by the ability to calculate the script of Bitcoin, it is very difficult to bring assets other than BTC into the lightning network. However, the RGB++ protocol can use CKB's Turing Complete Script System to realize the status channel and lightning network of CKB-based RGB++ assets.
With the above standards and functions, the RGB++ agreement is not limited to simple asset issuance scenarios like other Bitcoin host network programmable agreements, but supports complex applications such as asset transactions, asset lending, and CDP stabilizer coins. For example, RGB++ combined with the tied logic of the Bitcoin main network, the PSBT script can realize a DEX form of order book grid.
In the market competition for the programmatic realization of Bitcoin in Turing, DriveChain and the restoration of OPCAT operating codes and other programs require very large uncertainties and unpredictability due to changes in the Bitcoin agreement layer， UTXO compatible with Bitcoin L2 and EVM in the realist route is more recognized by developers and capital. UTXO is also composed of Bitcoin L2, represented by CKB. EVM is compatible with Bitcoin Rollup L2, represented by Merlin Chain and BOB.
To be practical, the Bitcoin L1 asset issuance agreement has just begun to form a local consensus in the Bitcoin community, and the community consensus of Bitcoin L2 is at an earlier stage. But in this frontier area, 《 Bitcoin magazine 》 and Pantera have tried to set the definition range for Bitcoin L2 by drawing on the conceptual structure of Taifang L2.
In their eyes, Bitcoin L2 should have the following three characteristics：
However, the weak state calculation and verification capabilities of the Bitcoin main network cannot achieve Feature 1 and Feature 2 in the short term. In this case, EVM compatible L2 is a chain expansion plan that is completely dependent on social trust assumptions，Although they are writing in white papers that future integration of BitVM for data availability verification and joint mining with the Bitcoin main network enhances safety.
Of course, this does not mean that these EVM compatibility Rollup L2 is fake Bitcoin L2, but that they do not strike a good balance between security, distrust and scalability. Moreover, the Bitcoin ecology introduces a complete solution with the Turing of Taifang, which is easily regarded by Bitcoin Maxi as appeasement for the expansionist route.
Therefore, UTXO and Bitcoin L2 are naturally superior to EVM compatible Rollup L2 in terms of orthodox and Bitcoin community consensus.
Characteristics of UTXO Stack: Fractal Bitcoin Main Network
If the Episcopal L2 is based on the fractal of the Taifang, then the Bitcoin L2 should be the fractal of Bitcoin.
The UTXO Stack of the CKB ecology activates UTXO bitcoin L2 for the developer's key and originally integrates the RGB++ protocol capability. This allows seamless interoperability between the Bitcoin main network and UTXO developed using UTXO Stack and Bitcoin L2. UTXO Stack supports the pledge of BTC, CKB and BTC L1 assets to ensure the safety of UTXO co-constructor Bitcoin L2.
UTXO Stack currently supports the free flow and interoperability of RGB++ assets between the Bitcoin Lightning Network-CKB Lightning Network-UTXO Stack parallel L2s. In addition, UTXO Stack also supports Runes, Atomicals, Taproot Asset, Stamps and other UTXO-based Bitcoin L1 programmability protocol assets to flow freely and interoperate between UTXO Stack parallel L2s-CKB Lightning Network-Bitcoin Lightning Network.
UTXO Stack introduced the modular paradigm into the construction field of Bitcoin L2, and cleverly bypassed the calculation of the Bitcoin main network status and the verification of data availability with the tie of the same structure. In this modular stack, the role of Bitcoin is the consensus layer and the settlement layer. The role of CKB is the data availability layer, while the roles of UTXO Stack parallel L2 are the execution layer.
But there is actually another perspective that regards bitcoin as APP Chain for digital gold. From this perspective, it is the positioning of the bottom layer of digital gold to centralize the ledger, which shapes the shape of the current Bitcoin main network UTXO set and the characteristics of programmable protocols. But if I remember correctly, Satoshi Nakamoto's vision is to make Bitcoin a P2P electronic currency. The demand for programmability in digital gold is safes and vaults, and the demand for programmability in currency is the central bank-commercial bank circulation network. Therefore, the programmability enhancement agreement of Bitcoin is not an outrageous behavior, but a return to the vision of Satoshi Nakamoto.
Drawing on Gartner Hype Cycle's research method, we can divide the Bitcoin programmability programs into 5 stages
Just as the evolution of convergence has occurred repeatedly in nature, it can be expected that the trend of the complete and programmable development of the Bitcoin eco-turing will show a certain degree of consistency with the Episcopal ecology in some respects. But this consistency will not simply be based on Taifang's technology stack to Bitcoin ecology, but on the use of Bitcoin's original technology stack （ programmability based on UTXO ） to achieve a similar ecological structure.
CKB's UTXO Stack is very similar to Optimism's OP Stack positioning. OP Stack maintains strong equivalence and consistency with the Israel-Pacific main network at the executive level, and UTXO Stack maintains strong equivalence with the Bitcoin main network at the executive level. And consistency. At the same time, UTXO Stack, like the OP Stack structure, is a parallel structure.
In the future, UTXO Stack will introduce RaaS services such as shared servers, shared security, shared liquidity, and shared verification sets to further reduce the cost and difficulty of developers to start UTXO co-constructor Bitcoin L2. At present, there are a large number of projects such as the Decentralized Stabilization Coin Agreement, AMM DEX, Borrowing Agreement, and Autonomous World. It is planned to use UTXO Stack to build UTXO co-constructor Bitcoin L2 as its bottom consensus infrastructure.
Unlike other Bitcoin security abstract agreements, the CKB's consensus mechanism is a PoW consensus mechanism consistent with the Bitcoin main network, and the machine algorithm maintains the consistency of the consensus ledger. But there is some difference between CKB's tokens economics and Bitcoin. In order to maintain the consistency of block space production and consumption behavior incentives, Bitcoin chose to introduce weights and vByte mechanism to calculate state space usage fees, and CKB chose to privatize state space.
CKB's tokens economics consists of two parts: basic distribution and secondary distribution. All CKBs issued on a basic basis are fully rewarded to miners. The purpose of CKB issued in the second level is to collect state rent. The specific distribution ratio of the issued in the second level depends on the current way in which CKBs are used in the network.
For example, suppose that 50% of all circulating CKBs are used for storage, 30% are locked in NervosDAO, and 20% are fully mobile. Then, 50% of （ issued in the second level, that is, the rent of the storage state ）, will be allocated to miners, 30% will be allocated to NervosDAO depositors, and the remaining 20% will be allocated to the Treasury Fund.
This tokens economic model can constrain overall growth, coordinate the interests of different network participants （ including users, miners, developers, and tokens holders ）, and create an incentive structure that is beneficial to everyone. This is different from other L1 situations in the market.
In addition, CKB allows a single Cell to occupy a maximum state space of 1,000 bytes, which gives the NFT assets on the CKB some other block chain similar assets that do not have strange characteristics, such as the original portability of Gas fees, the programmability of state space, etc. These bizarre characteristics make UTXO Stack very suitable for building digital physical reality for the infrastructure of autonomous world projects.
UTXO Stack allows Bitcoin L2 developers to use BTC, CKB, and other Bitcoin L1 asset pledges to participate in their network consensus.
Summary
It is inevitable that Bitcoin will develop to the stage of Turing's complete programmable program. But Turing’s complete programmability will not happen to the Bitcoin main network, but under the chain （RGB, BitVM） or Bitcoin L2 （CKB, EVM Rollup, DriveChain）.
According to historical experience, one of these agreements will eventually develop into a monopolistic standard agreement.
There are two key factors that determine the competitiveness of Bitcoin programmable agreements: 1. Realization of BTC's free flow between L1<>L2 without relying on additional social trust assumptions; 2. Attract developers, funds and users of sufficient scale into their L2 ecology.
As a programmable solution for bitcoin, CKB has used the co-constructed binding +CKB network to replace the customer verification solution to achieve the free flow of Bitcoin L1 assets between L1<>L2, and Does not rely on additional social trust assumptions. Moreover, the benefit is in the spatial privatization characteristics of CKB Cell, and RBG++ does not bring pressure to the Bitcoin main network to explode like other Bitcoin programmability agreements.
Recently, through RGB++~ the first batch of asset releases, the ecological thermal start was initially completed, and the new users and a group of new developers were150,000 new users for the CKB ecological success OnB. For example, OpenStamp, a one-stop solution for Stamps ecology in Bitcoin L1, has chosen to use UTXO Stack to construct UTXOs serving Stamps ecology and Bitcoin L2.
In the next stage, CKB will focus on ecological application construction, realizing BTC's free flow between L1<>L2, and integrating lightning networks, and strive to become a programmable layer of future bitcoins.
[1] What are the Key Properties of Bitcoin?
[2] Programmability of bitcoin
[3] ABCDE: Why should we invest in UTXO Stack
[4] LAYER 2 IS NOT A MAGIC INCANTATION
submitted by djminger007 to NervosNetwork [link] [comments]
Bullish; Heres the link for those that might want to cross reference
https://mirror.xyz/0xB239e7668B6dAF0122166E2De879Da87FF47858C/hkXPFe0uBy2fQNIzjVrL0rMUONj2hTJklaN14Rbguuk
Foreword
In the fourth round of bitcoin halving cycle, the outbreak of the Ordinals agreement and similar agreements was adopted to make the encryption industry aware of the positive externality of the security and ecological development of the bitcoin master network based on the Bitcoin L1 layer of issued assets and transaction assets. Value is the “Uniswap moment” of Bitcoin ecology.The programmable evolution and iteration of Bitcoin is the result of market governance in the Bitcoin community, not driven by the theory of Holder of BTC, Builder of block space, etc.
At present, by enhancing the programmability of Bitcoin and increasing the utilization rate of the block space of the main network of Bitcoin, it has become a new design space for the consensus of the Bitcoin community.
Unlike Etai and other high-performance public chains, in order to ensure the simplicity and light quantification of UTXO episodes, the design space for the programmability of bitcoins is highly restricted, and the basic constraints are how to use scripts and OP Code to operate UTXO.
The classic Bitcoin programmable program has a state channel （ Lightning Network ）, customer end verification （RGB）, side chain （Liquid Network, Stacks, RootSock, etc. ）, CounterParty, Omni Layer Asser, TaproC, etc. Emerging bitcoin programmability programs since 2023 include Ordinals, BRC20, Runes, Atomicals, Stamps, etc.
After the end of the second wave of inscriptions, a new generation of bitcoin programmability programs and so on emerged, such as CKB's UTXO co-construct binding program, EVM compatible bitcoin L2 program, DriveChain program, etc.
Compared with the EVM compatible bitcoin L2 scheme, CKB（Common Knowledge Base） The Bitcoin Programmability Program is a native, safe, and non-introducing social trust hypothesis solution in the Bitcoin Programmability Modern Design Space. Compared with the DriveChain plan, it does not require any change in the level of the Bitcoin agreement.
In the foreseeable future, the programmable growth curve of Bitcoin will go through an accelerated growth stage, and the assets, users, and applications of Bitcoin ecology will usher in a massive outbreak of martial arts，The UTXO Stack of the CKB ecology will provide new Bitcoin developers with the ability to build protocols using modular stacks. In addition, CKB is exploring the integration of the lightning network with UTXO Stack, using the original programmability of Bitcoin to achieve interoperability between the new agreements.
Programmable naming space for bitcoin
The block chain is a machine for creating trust, and the main Bitcoin network is the No. 0 machine. Like all philosophy in the West is a footnote to Plato, everything in the encrypted world （ assets, narratives, block chain networks, protocols, DAO, etc. ） are derivatives and derivatives of bitcoin.In the process of coordinated evolution of Bitcoin Maxi and expansionists, from whether the Bitcoin main network supports Turing’s complete struggle to the dispute between the isolation witness program and the large block expansion plan, Bitcoin is constantly split. This is not only creating new encryption projects and encryption community consensus, but also strengthening and consolidating Bitcoin's own community consensus, which is a process of completing self-identification while others are institutionalized.
Due to the mysterious disappearance of Satoshi Zhong, Bitcoin community governance does not exist in the governance structure of the “ enlightened monarchy ” like Taifang, but is a balanced governance model in open games by miners, developers, communities and markets. This gives Bitcoin a community consensus that once formed and is extremely stable.
The characteristics of the current Bitcoin community consensus are: consensus is not command and control, trust minimization, decentralization, anti-censorship, anonymity, open source, open collaboration, licensing exemption, legal neutrality, homogenization, forward compatibility, resources Use minimization, verification > calculation, convergence, transaction volatility、Resist DoS attacks, avoid scramble entry, robustness, consistent incentives, curing, consensus that should not be tampered with, conflicting principles, collaborative advancement, etc. [1]
The current form of the Bitcoin main network can be regarded as an example of the consensus characteristics of the above Bitcoin community. The programmable design space of Bitcoin is also defined by the consensus characteristics of the Bitcoin community.
Programmable classic design space for bitcoin
When other public chains try to be modular, parallel, etc. to explore the design space where the block chain cannot be a triangular solution, the design space of the bitcoin protocol has always focused on scripts, OP Code, and UTXO.Two typical examples are the two major upgrades to the Bitcoin main network since 2017, Segwit hard fork and Taproot soft fork.
In August 2017, Segwit bifurcated hard, adding 3M blocks outside the main block of 1M to save the signature （ Witness）, and setting the weight of the signature data as the main block when calculating the miner’s fee 1/4 to maintain consistency in the cost of spending a UTXO output and creating a UTXO output，Prevent the abuse of UTXO to zero to increase the expansion rate of UTXO sets.
In November 2021, Taproot's soft fork was introduced by introducing Schnorr's multiple signature program to save UTXO's verification time and block space occupied by multiple signatures.
UTXO（ The unspent transaction output ） is the basic data structure of the Bitcoin main network, which has atomic, non-homogeneous, and chain-coupled characteristics. Every transaction on the main net of Bitcoin consumes 1 UTXO as input, and creates an integer n new UTXO output. It is generally understood that UTXO can be regarded as a dollar, euro and other banknotes running on the chain. It can cost, change, split, combine, etc., but its minimum atomic unit is Satoshi（sats）. 1 UTXO represents the latest state at a particular time. UTXO episode, which represents the latest state of the Bitcoin main network at a certain time.
By maintaining the simplicity, light quantification, and easy verification of the Bitcoin UTXO episode, the state expansion rate of the Bitcoin main network has successfully stabilized at a level compatible with the hardware Moore law, thereby ensuring the participation of the entire Bitcoin network nodes And the robustness of transaction verification.
Correspondingly, the programmable design space of Bitcoin is also constrained by the consensus characteristics of the Bitcoin community. For example, in order to prevent potential security risks, Satoshi Nakamoto decided to remove the OP-CAT operation code in August 2010, which is the key logic for achieving programmability at the complete level of Bitcoin Turing.
Bitcoin's programmable realization path does not use the virtual machine （VM） scheme in the chain like Taifang and Solana, but chooses to use the script and operation code （OP Code） for UXTO, transaction Input field, output field and witness data （Witness）.
The main toolboxes for programmability of bitcoin are: multiple signatures, time locks, Hash locks, process control （OP_IF, OP_ELIF）. [2]
Under the classic design space, the programmability of bitcoin is very limited. It only supports a few verification procedures, but does not support chain storage and chain calculations, and chain storage and chain calculations are precisely to achieve Turing's complete level programmability. Core functional components.
Programmable Renaissance of Bitcoin
But Bitcoin's programmable design space is not a fixed state. Instead, it is closer to a dynamic spectrum that changes over time.Unlike the outside world's stereotype that the development of the Bitcoin main network is at a standstill, in the case of various consensus vectors limiting the design space, the development, deployment, adoption, and promotion of the new script and new operation code of the Bitcoin main network are always in progress Times，And at some point even triggered a fork war in the encrypted community （ such as Segwit hard fork ）.
Taking the Bitcoin main net script type with degree change as an example, we can clearly perceive the changes. We can divide the scripts used by the Bitcoin main network output type into three categories: original script pubkey, pubkeyhash, enhanced script multisig, scripthash, witness script witness_v0_keyhash, witness_v0_scripthash, witness_v1_taproot.
From the change trend chart of the entire historical output type of the Bitcoin main network, we observe a basic fact: the programmability enhancement of the Bitcoin main network is a long-term historical trend, enhancing the share of scripts in the original script, and witnessing the script being swallowed The share of the enhanced script. The Ordinals agreement based on Segweit's enhanced script and Taproot's witness script opened a wave of Bitcoin L1 asset issuance, which is both a continuation of the programmable historical trend of the Bitcoin main network and a new stage of programmability of the Bitcoin main network.
The Bitcoin main network operation code also has an evolutionary process similar to the Bitcoin main net script.
For example, the Ordinals agreement is to achieve its functional design by combining the Bitcoin main net script taproot script-path spend and operation code （OP_FALSE, OP_IF, OP_PUSH, OP_ENDIF）.
Before the official birth of the Ordinals agreement, the programmable classic plan of bitcoin mainly has the state channel （ Lightning Network ）, customer verification （RGB）, side chain （Liquid Network, Stacks, RootSock, etc.）, CounterParty, etc.
The Ordinals agreement sequences the smallest atomized unit of UXTO （Satoshi）, and then inserts the data content in the Witness field of UTXO, and is associated with a specific deafness after sequencing, and then the chain indexer is responsible for indexing and Perform programmable operations of these data states. This new bitcoin programmability paradigm is vividly likened to “ Golden Eagle ”.
The new paradigm of the Ordinals agreement has inspired a wider range of encrypted communities to use the Bitcoin main network block space to distribute, cast and trade NFT collections and MeMe-type Token（, which can be collectively referred to as the inscription ）. For the first time in life, you have your own Bitcoin address.
However, the programmability of the Ordinals agreement inherits the limited programmability of Bitcoin and only supports the three functional methods of Deploy, Mint and Transfer. This allows the Ordinals agreement and its followers BRC20, Runes, Atomicals, Stamps, etc. to apply only to the application scenes where assets are issued. Support for DeFi application scenes such as transactions and loans that require state calculation and state storage is relatively weak.
Liquidity is the source of vitality for assets. Due to the natural characteristics of the programmability agreement of the Ordinals type bitcoin, the reissue of the inscription assets and the provision of light liquidity affect the value of the entire life cycle of the inscription assets.
Moreover, the Ordinals and BRC20 agreements are also suspected of misusing the witness data space and objectively causing the explosion of the main network of Bitcoin.
As a reference system, the main sources of the Pacific Master Network Gas fee are DEX transaction Gas fee, L2 data availability fee, and stable currency transfer Gas fee. Compared with the Taifang main network, the income type of the Bitcoin main network is single, cyclical, and the volatility rate is large.
The programmability of the Bitcoin main network cannot yet meet the demand for the space supply side of the Bitcoin main network block. To achieve a stable and sustainable block space income state with the Pacific Master Network, the original DEX, stable currency and L2 of the Bitcoin ecology are required. The prerequisite for the realization of these agreements and applications is that Bitcoin programmable agreements need to provide Turing's complete programming capabilities.
Therefore, how to achieve the complete programmability of Bitcoin Turing in its original place, while constraining the negative impact on the size of the Bitcoin main network, has become a current manifestation of Bitcoin ecology.
Bitcoin programmable CKB scheme
At present, the complete programmable programs for the original Turing of Bitcoin are: BitVM, RGB, CKB, EVM compatible with Rollup L2, DriveChain, etc.BitVM uses a group of OP Code in Bitcoin to build and non-logical doors, and then builds other basic logical doors with non-logical doors. Eventually, these basic logical gate circuits construct a VM native to Bitcoin. This principle is somewhat similar to the array of the Qin king of the famous science fiction novel 《 Tripartite 》. There are specific scenes in the TV series of the same name adapted by Netflix. The paper of the BitVM program has been completely open source, and is highly expected by the encrypted community. However, its engineering implementation is very difficult. It is difficult to land in the short term when it encounters problems such as data management costs under the chain, the number of participants, challenges-response interactions, and the complexity of the Hash function.
The RGB protocol uses customer end verification and one-time sealing technology to achieve the complete programmability of Turing. The core design idea is to store the status and logic of the smart contract in the output of the bitcoin transaction （Transaction）On the implementation of the maintenance and data storage of the smart contract code under the chain，The main network of bitcoins serves as the commitment layer of the final state.
EVM compatible with Rollup L2 is a quick plan to rebuild Bitcoin L2 with a mature Rollup L2 stack. However, given that the Bitcoin main network is currently unable to support fraud certification/validity certification, Rollup L2 needs to introduce the social trust assumption （ over-sign ）.
DriveChain is a side chain expansion plan. The basic design idea is to use Bitcoin as the bottom layer of the block chain, and to create side chains by locking Bitcoin to achieve two-way interoperability between Bitcoin and side chains. The realization of the DriveChain project requires agreement-level changes to Bitcoin, which will deploy the BIP300 and BIP301 proposed by the development team to the main network.
The above Bitcoin programmability plan is either extremely difficult to land in the short term, or introduces too many social trust assumptions, or requires agreement-level changes to Bitcoin.
Bitcoin L1 Asset Agreement: RGB++
In response to the shortcomings and problems of the programmability agreement in Bitcoin above, the CKB team gave a relatively balanced solution. The solution consists of Bitcoin L1 asset agreement RGB++, Bitcoin L2 Raas service provider UTXO Stack and interoperability agreement integrated with the lightning network.Original language of UXTO: tied to the same organization
RGB++ is a bitcoin L1 asset issuance agreement based on RGB design ideas. The project of RGB++ was realized, while inheriting the technical original words of CKB and RBG. It uses RGB's “ one-time seal ” and customer end verification technology, and at the same time tied up the UTXO（ expanded version of Cell） that maps Bitcoin UTXO to the CKB main network, and uses CKB and Bitcoin chains Script constraints to verify the accuracy of status calculations and the validity of ownership changes.
In other words, RGB++ uses Cell on the CKB chain to express the ownership relationship of RGB assets. It moves the asset data originally stored at the end of the RGB customer to the CKB chain and expresses it in the form of Cell. It establishes a mapping relationship with Bitcoin UTXO, allowing CKB to act as an open database and chain of RGB assets. Settlement layer, replacing RGB client，Achieve more reliable data hosting and RGB contract interaction.
Cell is the basic data storage unit of CKB and can contain various data types, such as CKBytes, tokens, TypeScript codes or sequencing data （ such as the JSON string ）. Each Cell contains a small program called Lock Script, which defines the owner of Cell. Lock Script not only supports the scripts of the Bitcoin main network, such as multiple signatures, Hash locks, time locks, etc., but also allows a Type Script to enforce specific rules to control its use. This allows developers to customize smart contracts according to different usages, such as issuing NFT, airdropping tokens, AMM Swap, etc.
The RGB protocol adds the root of the transaction under the chain to a UTXO'output by using the OP RETURN operating code, and uses UTXO as a container of status information. Then, RGB++ map this state information container constructed by RGB to Cell in CKB, keep the state information in Cell's type and data, and use this container UTXO as the Cell state owner.
As shown in the figure above, a complete RGB++ transaction life cycle is as follows：
- Calculation under the chain. When initiating a Tx bound by the same configuration, first choose a new UTXO btc_utxo#2 of the Bitcoin main network as a one-time sealed container, and then bind the UTXO btc_utxo#1 of the original Cell co-construct under the chain Btc_utxo#2、Using the original Cell as a CKB TX to enter the new Cel as an output to perform Hashi calculations to generate a commitment.
- Submit Bitcoin transactions. RGB++ initiated a Tx of the main bitcoin network, which will use btc_utxo#1 bound to the original Cell co-organizer as an input, and use OP RETURN to use the promise generated in the previous step as an output.
- Submit CKB transactions. CKB Tx calculated and generated under the chain before the execution of the CKB main network.
- Verify on the chain. The CKB main network runs a Bitcoin main network light client to verify the state change of the entire system. This is very different from RGB. The P2P mechanism used in the verification of RGB's status change requires that the initiator of Tx and the receiver be online at the same time and only interactively verify the relevant TX spectrum.
- Customer end verification with enhanced blockchain. RGB++ allows users to choose to use PoW to maintain consensus security CKB verification status calculations and URXO-Cell ownership changes.
- Trading folding. RGB++ supports the mapping of multiple Cells to a single UTXO, thereby achieving the elastic expansion of RGB++.
- Unowned smart contracts and shared status. A major difficulty in achieving a complete intelligent contract for Turing in the UTXO state data structure is the unowned intelligent contract and shared state. RGB++ can use CKB's overall state Cell and Cell of Intent to solve this problem.
- Non-interactive transfer. RGB++ turns RGB’s client verification process into an option, and no longer requires interactive transfers. If the user chooses CKB verification status calculation and ownership change, the interactive experience of the transaction is consistent with the Bitcoin main network.
To trust L1<>L2 interoperability: Leap
The tied tie of the same structure of RGB++ is a common logic for the realization of a common atom, which either occurs at the same time or flips at the same time without intermediate states. All RGB++ transactions will appear simultaneously on the BTC and CKB chains. The former is compatible with the transactions of the RGB agreement, while the latter replaces the process of customer end verification. The user only needs to check the relevant transactions on the CKB to verify whether the calculation of the status of the RGB++ transaction is correct. However, users may also use the transaction on the CKB chain as the verification basis, and use the local Tx map of UTXO to independently verify the RGB++ transaction. （Part of the functions such as transaction folding still need to rely on CKB block Hashi for anti-double flower verification ）
Therefore, the asset cross-chain between RGB++ and the CKB main network does not rely on the introduction of additional social trust assumptions, such as the relay layer of the cross-chain bridge, the centralized multi-sign vault of EVM compatible Rollup, etc. RGB++ Assets can be transferred from the Bitcoin main network to the CKB main network, or from the CKB main network to the Bitcoin main network. CKB calls this cross-chain workflow Leap.
RGB++ and CKB are loosely coupled. In addition to the assets supporting the Bitcoin L 1st floor （ are not limited to the original assets of the RGB++ agreement, including assets issued by Runes, Atomicals, Taproot Asset and other agreements ）Leap to CKB, RGB++The other support Leap to Cardan. At the same time, RGB++ also supports Bitcoin L2 assets Leap to Bitcoin main network.
Examples of extended functions and applications of RGB++
The RGB++ agreement originally supported the issuance of homogenized tokens and NFT.
The homogenized token standard of RGB++ is xUDT, and the NFT standard is Spore.
The xUDT standard supports a variety of homogenized tokens issuance methods, including but not limited to centralized distribution, airdrops, subscriptions, etc. The total amount of tokens can also be selected between the upper limit and the upper limit. For the tokens with a preset upper limit, a status sharing scheme can be used to verify whether the total number of each issuance is less than or equal to the preset upper limit.
Spore in the NFT standard will store all metadata on the chain, achieving 100% data availability security. Assets issued by the Spore Agreement DOB（Digital Object, digital object）, similar to Ordinals NFT, but with richer characteristics and play methods.
As a customer verification agreement, the RGB protocol naturally supports state channels and lightning networks, but is limited by the ability to calculate the script of Bitcoin, it is very difficult to bring assets other than BTC into the lightning network. However, the RGB++ protocol can use CKB's Turing Complete Script System to realize the status channel and lightning network of CKB-based RGB++ assets.
With the above standards and functions, the RGB++ agreement is not limited to simple asset issuance scenarios like other Bitcoin host network programmable agreements, but supports complex applications such as asset transactions, asset lending, and CDP stabilizer coins. For example, RGB++ combined with the tied logic of the Bitcoin main network, the PSBT script can realize a DEX form of order book grid.
Bitcoin L2 RaaS service provider: UTXO Stack
UTXO is the same as Bitcoin L2 Vs EVM compatible Bitcoin Rollup L2In the market competition for the programmatic realization of Bitcoin in Turing, DriveChain and the restoration of OPCAT operating codes and other programs require very large uncertainties and unpredictability due to changes in the Bitcoin agreement layer， UTXO compatible with Bitcoin L2 and EVM in the realist route is more recognized by developers and capital. UTXO is also composed of Bitcoin L2, represented by CKB. EVM is compatible with Bitcoin Rollup L2, represented by Merlin Chain and BOB.
To be practical, the Bitcoin L1 asset issuance agreement has just begun to form a local consensus in the Bitcoin community, and the community consensus of Bitcoin L2 is at an earlier stage. But in this frontier area, 《 Bitcoin magazine 》 and Pantera have tried to set the definition range for Bitcoin L2 by drawing on the conceptual structure of Taifang L2.
In their eyes, Bitcoin L2 should have the following three characteristics：
- Use bitcoin as a native asset. Bitcoin L2 must use Bitcoin as its main settlement asset.
- Use bitcoin as a settlement mechanism to enforce transactions. Users of Bitcoin L2 must be able to force their return to their first-tier asset control （ credible or untrustworthy ）.
- Demonstrate functional dependence on bitcoin. If the Bitcoin main network fails but the Bitcoin L2 system is still operational, then the system is not L2 of Bitcoin. [4]
However, the weak state calculation and verification capabilities of the Bitcoin main network cannot achieve Feature 1 and Feature 2 in the short term. In this case, EVM compatible L2 is a chain expansion plan that is completely dependent on social trust assumptions，Although they are writing in white papers that future integration of BitVM for data availability verification and joint mining with the Bitcoin main network enhances safety.
Of course, this does not mean that these EVM compatibility Rollup L2 is fake Bitcoin L2, but that they do not strike a good balance between security, distrust and scalability. Moreover, the Bitcoin ecology introduces a complete solution with the Turing of Taifang, which is easily regarded by Bitcoin Maxi as appeasement for the expansionist route.
Therefore, UTXO and Bitcoin L2 are naturally superior to EVM compatible Rollup L2 in terms of orthodox and Bitcoin community consensus.
Characteristics of UTXO Stack: Fractal Bitcoin Main Network
If the Episcopal L2 is based on the fractal of the Taifang, then the Bitcoin L2 should be the fractal of Bitcoin.
The UTXO Stack of the CKB ecology activates UTXO bitcoin L2 for the developer's key and originally integrates the RGB++ protocol capability. This allows seamless interoperability between the Bitcoin main network and UTXO developed using UTXO Stack and Bitcoin L2. UTXO Stack supports the pledge of BTC, CKB and BTC L1 assets to ensure the safety of UTXO co-constructor Bitcoin L2.
UTXO Stack currently supports the free flow and interoperability of RGB++ assets between the Bitcoin Lightning Network-CKB Lightning Network-UTXO Stack parallel L2s. In addition, UTXO Stack also supports Runes, Atomicals, Taproot Asset, Stamps and other UTXO-based Bitcoin L1 programmability protocol assets to flow freely and interoperate between UTXO Stack parallel L2s-CKB Lightning Network-Bitcoin Lightning Network.
UTXO Stack introduced the modular paradigm into the construction field of Bitcoin L2, and cleverly bypassed the calculation of the Bitcoin main network status and the verification of data availability with the tie of the same structure. In this modular stack, the role of Bitcoin is the consensus layer and the settlement layer. The role of CKB is the data availability layer, while the roles of UTXO Stack parallel L2 are the execution layer.
Bitcoin's programmable growth curve and CKB's future
Bitcoin's programmable growth curve and CKB's future
In fact, there is an inherent tension between Bitcoin’s digital gold narrative and Bitcoin’s programmable narrative. Some OGs in the Bitcoin community regard the Bitcoin L1 programmable agreement that has emerged since 23 years as a new round of Bitcoin main network. Dust attack boom. To some extent, the saliva war between the core developer of Bitcoin, Luke, and the fans of BRC20, is the third world war between Bitcoin maxi and the expanders following the battle for the completeness of Turing and the block.But there is actually another perspective that regards bitcoin as APP Chain for digital gold. From this perspective, it is the positioning of the bottom layer of digital gold to centralize the ledger, which shapes the shape of the current Bitcoin main network UTXO set and the characteristics of programmable protocols. But if I remember correctly, Satoshi Nakamoto's vision is to make Bitcoin a P2P electronic currency. The demand for programmability in digital gold is safes and vaults, and the demand for programmability in currency is the central bank-commercial bank circulation network. Therefore, the programmability enhancement agreement of Bitcoin is not an outrageous behavior, but a return to the vision of Satoshi Nakamoto.
Drawing on Gartner Hype Cycle's research method, we can divide the Bitcoin programmability programs into 5 stages
- Technology budding period: DriveChain, UTXO Stack, BitVM, etc.
- Expected expansion period: Runes, RGB++, EVM Rollup bitcoin L2, etc.
- Foam burst period: BRC20, Atomicals, etc.
- Steady recovery period: RGB, lightning network, bitcoin side chain, etc.
- Mature plateau period: bitcoin script, Taproot script, Hash time lock, etc.
The future of CKB: OP Stack+Eigenlayer
Whether it is EVM compatible with Bitcoin Rollup L2, UTXO co-constructor Bitcoin L2, or Drive Chain and other new paradigms, Turing’s complete programmable implementation of various programs ultimately points to the Bitcoin main network as a consensus and settlement layer.Just as the evolution of convergence has occurred repeatedly in nature, it can be expected that the trend of the complete and programmable development of the Bitcoin eco-turing will show a certain degree of consistency with the Episcopal ecology in some respects. But this consistency will not simply be based on Taifang's technology stack to Bitcoin ecology, but on the use of Bitcoin's original technology stack （ programmability based on UTXO ） to achieve a similar ecological structure.
CKB's UTXO Stack is very similar to Optimism's OP Stack positioning. OP Stack maintains strong equivalence and consistency with the Israel-Pacific main network at the executive level, and UTXO Stack maintains strong equivalence with the Bitcoin main network at the executive level. And consistency. At the same time, UTXO Stack, like the OP Stack structure, is a parallel structure.
In the future, UTXO Stack will introduce RaaS services such as shared servers, shared security, shared liquidity, and shared verification sets to further reduce the cost and difficulty of developers to start UTXO co-constructor Bitcoin L2. At present, there are a large number of projects such as the Decentralized Stabilization Coin Agreement, AMM DEX, Borrowing Agreement, and Autonomous World. It is planned to use UTXO Stack to build UTXO co-constructor Bitcoin L2 as its bottom consensus infrastructure.
Unlike other Bitcoin security abstract agreements, the CKB's consensus mechanism is a PoW consensus mechanism consistent with the Bitcoin main network, and the machine algorithm maintains the consistency of the consensus ledger. But there is some difference between CKB's tokens economics and Bitcoin. In order to maintain the consistency of block space production and consumption behavior incentives, Bitcoin chose to introduce weights and vByte mechanism to calculate state space usage fees, and CKB chose to privatize state space.
CKB's tokens economics consists of two parts: basic distribution and secondary distribution. All CKBs issued on a basic basis are fully rewarded to miners. The purpose of CKB issued in the second level is to collect state rent. The specific distribution ratio of the issued in the second level depends on the current way in which CKBs are used in the network.
For example, suppose that 50% of all circulating CKBs are used for storage, 30% are locked in NervosDAO, and 20% are fully mobile. Then, 50% of （ issued in the second level, that is, the rent of the storage state ）, will be allocated to miners, 30% will be allocated to NervosDAO depositors, and the remaining 20% will be allocated to the Treasury Fund.
This tokens economic model can constrain overall growth, coordinate the interests of different network participants （ including users, miners, developers, and tokens holders ）, and create an incentive structure that is beneficial to everyone. This is different from other L1 situations in the market.
In addition, CKB allows a single Cell to occupy a maximum state space of 1,000 bytes, which gives the NFT assets on the CKB some other block chain similar assets that do not have strange characteristics, such as the original portability of Gas fees, the programmability of state space, etc. These bizarre characteristics make UTXO Stack very suitable for building digital physical reality for the infrastructure of autonomous world projects.
UTXO Stack allows Bitcoin L2 developers to use BTC, CKB, and other Bitcoin L1 asset pledges to participate in their network consensus.
Summary
It is inevitable that Bitcoin will develop to the stage of Turing's complete programmable program. But Turing’s complete programmability will not happen to the Bitcoin main network, but under the chain （RGB, BitVM） or Bitcoin L2 （CKB, EVM Rollup, DriveChain）.
According to historical experience, one of these agreements will eventually develop into a monopolistic standard agreement.
There are two key factors that determine the competitiveness of Bitcoin programmable agreements: 1. Realization of BTC's free flow between L1<>L2 without relying on additional social trust assumptions; 2. Attract developers, funds and users of sufficient scale into their L2 ecology.
As a programmable solution for bitcoin, CKB has used the co-constructed binding +CKB network to replace the customer verification solution to achieve the free flow of Bitcoin L1 assets between L1<>L2, and Does not rely on additional social trust assumptions. Moreover, the benefit is in the spatial privatization characteristics of CKB Cell, and RBG++ does not bring pressure to the Bitcoin main network to explode like other Bitcoin programmability agreements.
Recently, through RGB++~ the first batch of asset releases, the ecological thermal start was initially completed, and the new users and a group of new developers were
In the next stage, CKB will focus on ecological application construction, realizing BTC's free flow between L1<>L2, and integrating lightning networks, and strive to become a programmable layer of future bitcoins.
[1] What are the Key Properties of Bitcoin?
[2] Programmability of bitcoin
[3] ABCDE: Why should we invest in UTXO Stack
[4] LAYER 2 IS NOT A MAGIC INCANTATION
2024.04.29 00:26 RBTV_Sendeplan_Bot Sendeplan-Thread der Kalenderwoche 18 des Jahres 2024
Uploads vom Montag, dem 29. April 2024
17:14 [U] Bohndesliga - HOENEẞ vs. TUCHEL: Round 1! UND: Spitzenspiel XXL Bohndesliga 31. Spieltag 2023/24
18:00 [U] Speedrundale - SILENT HILL 2 (New Game) Speedrun in 39:08 von DizzySplits
19:00 [U] Der Monatsausblick - PEN AND PAPER MIT UKE, Strategie-Gipfel uvm. Das geht im Mai
Uploads vom Dienstag, dem 30. April 2024
09:30 [U] Bohndesliga International - WEMBLEY Reloaded? Preview CHAMPIONS LEAGUE HALBFINALE
17:30 [U] Du bist! - Besiegen sie die PANDEMIE? PANDEMIC
18:00 [U] Game Talk - HADES II: Unterwelt der Oberklasse – Wir haben’s gespielt!
Programm vom Donnerstag, dem 2. Mai 2024
18:00 [L] Let’s Play - INDIKA mit Colin & Krogi (120 Minuten)
20:00 [L] RBTV Home - Die BohnGemeinschaft freut sich auf euch! (165 Minuten)
Uploads vom Donnerstag, dem 2. Mai 2024
15:26 [U] Bohndesliga Extra - RANGNICK SAGT AB! Niemand will Bayern-Trainer werden!!! Reaction BOHNDESLIGA
18:00 [U] Retro Klub - BESSER ALS KINO? Videogames als Film-Sequels #2
18:30 [U] Kino+ Spezial - Was macht gute VISUAL EFFECTS & CGI aus? Talk mit VFX-Profi
23:00 [U] RBTV Home - Diese Show ist ein FIEBERTAUM! Florentin kriegt ein LIEBESLIED!
Programm vom Freitag, dem 3. Mai 2024
18:00 [L] Let’s Play - RBTVs Most Favorite Star Wars Games (115 Minuten)
20:00 [L] Nerds an Herds - Garfield Spezial (185 Minuten)
Uploads vom Freitag, dem 3. Mai 2024
16:00 [U] Let’s Play - SOWAS spielt man nicht alle Tage!! INDIKA mit Colin & Krogi
Uploads vom Samstag, dem 4. Mai 2024
12:00 [U] Game Two - No Rest for the Wicked, Top Spin 2K25, Sand Land Game Two #332
15:00 [U] Nerds an Herds - GARFIELDs Lasagne-Schlacht Nerds an Herds mit Eddy, Mel, Antje & Schröck
16:00 [U] Let’s Play - Wir spielen unsere LIEBSTEN STAR WARS GAMES aller Zeiten
Uploads vom Sonntag, dem 5. Mai 2024
16:00 [U] Let’s Play - Du-Du-Du-DUELL! 2 Tennis-Nerds testen TOPSPIN 2K25
00:00 [U] LOOTEN & LEVELN - City of Mist: Das Lazarus Projekt Folge 7
Livestreams vom Montag, dem 29. April 2024
12:25 [L] Krogmann streamt - Skateboard fahren ???????? !yt !support (Open End)
19:10 [L] Etienne streamt - Reactions über Reactions! !löwenanteil !scalable (290 Minuten)
19:30 [L] Nils streamt - Fallout 4: Zurück im Wasteland (PC-Version) (Open End)
Livestreams vom Dienstag, dem 30. April 2024
09:10 [L] Krogmann streamt - IRLsen ???????? !yt !support (Open End)
14:20 [L] Krogmann streamt - ⭐️DRAGONS DOGMA 2⭐️ !yt !support (Open End)
14:25 [L] Etienne streamt - Ist Gray Zone Warfare der Tarkov-Killer? #werbung !löwenanteil !scalable (Open End)
17:20 [L] Nils streamt - Rötzlingen rult! Manor Lords! Danach Albion mit @Radlerauge ! (Open End)
18:55 [L] Radlerauge streamt - MEGALOPOLIS Challenge (10.000 Einwohner?) in Manor Lords (480 Minuten)
19:00 [L] Nils streamt - Auf ins Abenteuer! Albion mit @Radlerauge !albion #Werbung (Open End)
01:05 [L] Simon streamt - AFTER DARK Mitternachts-Zock mit MASTER OF PUPPETS, POOLS und BACKROOMS BREAK (Open End)
Livestreams vom Mittwoch, dem 1. Mai 2024
12:20 [L] Simon streamt - Der neue REMNANT II - DLC 2 "THE FORGOTTEN KINGDOM" wird angespielt! #werbung (Open End)
Livestreams vom Donnerstag, dem 2. Mai 2024
11:00 [L] Krogmann streamt - zu arbeit gehen ???????? !yt !support (Open End)
18:10 [L] Etienne streamt - EDMUNDENZEL ist zurück in Gray Zone Warfare! Mit @denzelzockt !löwenanteil !scalable (Open End)
20:00 [L] Radlerauge streamt - MEGALOPOLIS Challenge (10.000 Einwohner?) in Manor Lords (Open End)
Livestreams vom Freitag, dem 3. Mai 2024
12:35 [L] Krogmann streamt - Das tollste Dorf errichten in Manor Lords ???????? Her mit euren Tips! !yt !support (Open End)
20:05 [L] Radlerauge streamt - FRANZ Federer und der Grand Slam (Open End)
Livestreams vom Samstag, dem 4. Mai 2024
19:55 [L] Radlerauge streamt - Conquest-Challenge auf maximaler Schwierigkeit in Manor Lords (Open End)
Livestreams vom Sonntag, dem 5. Mai 2024
19:55 [L] Etienne streamt - RELEASE RADAR - was erscheint im Mai? !löwenanteil !scalable (Open End)
20:20 [L] Radlerauge streamt - Conquest-Challenge auf maximaler Schwierigkeit in Manor Lords (Open End)
VOD-Uploads der letzten 7 Tage
29.04.2024 17:14 Bohndesliga - HOENEẞ vs. TUCHEL: Round 1! UND: Spitzenspiel XXL Bohndesliga 31. Spieltag 2023/24
29.04.2024 18:00 Speedrundale - SILENT HILL 2 (New Game) Speedrun in 39:08 von DizzySplits
29.04.2024 19:00 Der Monatsausblick - PEN AND PAPER MIT UKE, Strategie-Gipfel uvm. Das geht im Mai
30.04.2024 09:30 Bohndesliga International - WEMBLEY Reloaded? Preview CHAMPIONS LEAGUE HALBFINALE
30.04.2024 17:30 Du bist! - Besiegen sie die PANDEMIE? PANDEMIC
30.04.2024 18:00 Game Talk - HADES II: Unterwelt der Oberklasse – Wir haben’s gespielt!
02.05.2024 15:26 Bohndesliga Extra - RANGNICK SAGT AB! Niemand will Bayern-Trainer werden!!! Reaction BOHNDESLIGA
02.05.2024 18:00 Retro Klub - BESSER ALS KINO? Videogames als Film-Sequels #2
02.05.2024 18:30 Kino+ Spezial - Was macht gute VISUAL EFFECTS & CGI aus? Talk mit VFX-Profi
02.05.2024 23:00 RBTV Home - Diese Show ist ein FIEBERTAUM! Florentin kriegt ein LIEBESLIED!
03.05.2024 16:00 Let’s Play - SOWAS spielt man nicht alle Tage!! INDIKA mit Colin & Krogi
04.05.2024 12:00 Game Two - No Rest for the Wicked, Top Spin 2K25, Sand Land Game Two #332
04.05.2024 15:00 Nerds an Herds - GARFIELDs Lasagne-Schlacht Nerds an Herds mit Eddy, Mel, Antje & Schröck
04.05.2024 16:00 Let’s Play - Wir spielen unsere LIEBSTEN STAR WARS GAMES aller Zeiten
05.05.2024 16:00 Let’s Play - Du-Du-Du-DUELL! 2 Tennis-Nerds testen TOPSPIN 2K25
Weiterführende Links
Die vollständige Liste aller Livestreams von RBTV ist unter https://rocketbeans.tv/livestreams zu finden.
Der Uploadplan mit allen Uploads dieser Woche ist hier https://rocketbeans.tv/mediathek/uploadplan.
Kurzfristige YouTube-Upload-Änderungen werden im Forum in diesem Thread kommuniziert https://forum.rocketbeans.tv/t/rbtv-youtube-uploads-channel-managment-ticke91004/9999.
Unter https://redd.it/if366o wird eine Liste von gerade streamenden Bohnen bzw. VoDs ihrer letzten Livestream-Sessions gepflegt.
Alle Folgen von MoinMoin schaut Maskedminds in diesem Thread https://redd.it/y4ih4j
submitted by RBTV_Sendeplan_Bot to rocketbeans [link] [comments]
17:14 [U] Bohndesliga - HOENEẞ vs. TUCHEL: Round 1! UND: Spitzenspiel XXL Bohndesliga 31. Spieltag 2023/24
18:00 [U] Speedrundale - SILENT HILL 2 (New Game) Speedrun in 39:08 von DizzySplits
19:00 [U] Der Monatsausblick - PEN AND PAPER MIT UKE, Strategie-Gipfel uvm. Das geht im Mai
Uploads vom Dienstag, dem 30. April 2024
09:30 [U] Bohndesliga International - WEMBLEY Reloaded? Preview CHAMPIONS LEAGUE HALBFINALE
17:30 [U] Du bist! - Besiegen sie die PANDEMIE? PANDEMIC
18:00 [U] Game Talk - HADES II: Unterwelt der Oberklasse – Wir haben’s gespielt!
Programm vom Donnerstag, dem 2. Mai 2024
18:00 [L] Let’s Play - INDIKA mit Colin & Krogi (120 Minuten)
20:00 [L] RBTV Home - Die BohnGemeinschaft freut sich auf euch! (165 Minuten)
Uploads vom Donnerstag, dem 2. Mai 2024
15:26 [U] Bohndesliga Extra - RANGNICK SAGT AB! Niemand will Bayern-Trainer werden!!! Reaction BOHNDESLIGA
18:00 [U] Retro Klub - BESSER ALS KINO? Videogames als Film-Sequels #2
18:30 [U] Kino+ Spezial - Was macht gute VISUAL EFFECTS & CGI aus? Talk mit VFX-Profi
23:00 [U] RBTV Home - Diese Show ist ein FIEBERTAUM! Florentin kriegt ein LIEBESLIED!
Programm vom Freitag, dem 3. Mai 2024
18:00 [L] Let’s Play - RBTVs Most Favorite Star Wars Games (115 Minuten)
20:00 [L] Nerds an Herds - Garfield Spezial (185 Minuten)
Uploads vom Freitag, dem 3. Mai 2024
16:00 [U] Let’s Play - SOWAS spielt man nicht alle Tage!! INDIKA mit Colin & Krogi
Uploads vom Samstag, dem 4. Mai 2024
12:00 [U] Game Two - No Rest for the Wicked, Top Spin 2K25, Sand Land Game Two #332
15:00 [U] Nerds an Herds - GARFIELDs Lasagne-Schlacht Nerds an Herds mit Eddy, Mel, Antje & Schröck
16:00 [U] Let’s Play - Wir spielen unsere LIEBSTEN STAR WARS GAMES aller Zeiten
Uploads vom Sonntag, dem 5. Mai 2024
16:00 [U] Let’s Play - Du-Du-Du-DUELL! 2 Tennis-Nerds testen TOPSPIN 2K25
00:00 [U] LOOTEN & LEVELN - City of Mist: Das Lazarus Projekt Folge 7
Livestreams vom Montag, dem 29. April 2024
12:25 [L] Krogmann streamt - Skateboard fahren ???????? !yt !support (Open End)
19:10 [L] Etienne streamt - Reactions über Reactions! !löwenanteil !scalable (290 Minuten)
19:30 [L] Nils streamt - Fallout 4: Zurück im Wasteland (PC-Version) (Open End)
Livestreams vom Dienstag, dem 30. April 2024
09:10 [L] Krogmann streamt - IRLsen ???????? !yt !support (Open End)
14:20 [L] Krogmann streamt - ⭐️DRAGONS DOGMA 2⭐️ !yt !support (Open End)
14:25 [L] Etienne streamt - Ist Gray Zone Warfare der Tarkov-Killer? #werbung !löwenanteil !scalable (Open End)
17:20 [L] Nils streamt - Rötzlingen rult! Manor Lords! Danach Albion mit @Radlerauge ! (Open End)
18:55 [L] Radlerauge streamt - MEGALOPOLIS Challenge (10.000 Einwohner?) in Manor Lords (480 Minuten)
19:00 [L] Nils streamt - Auf ins Abenteuer! Albion mit @Radlerauge !albion #Werbung (Open End)
01:05 [L] Simon streamt - AFTER DARK Mitternachts-Zock mit MASTER OF PUPPETS, POOLS und BACKROOMS BREAK (Open End)
Livestreams vom Mittwoch, dem 1. Mai 2024
12:20 [L] Simon streamt - Der neue REMNANT II - DLC 2 "THE FORGOTTEN KINGDOM" wird angespielt! #werbung (Open End)
Livestreams vom Donnerstag, dem 2. Mai 2024
11:00 [L] Krogmann streamt - zu arbeit gehen ???????? !yt !support (Open End)
18:10 [L] Etienne streamt - EDMUNDENZEL ist zurück in Gray Zone Warfare! Mit @denzelzockt !löwenanteil !scalable (Open End)
20:00 [L] Radlerauge streamt - MEGALOPOLIS Challenge (10.000 Einwohner?) in Manor Lords (Open End)
Livestreams vom Freitag, dem 3. Mai 2024
12:35 [L] Krogmann streamt - Das tollste Dorf errichten in Manor Lords ???????? Her mit euren Tips! !yt !support (Open End)
20:05 [L] Radlerauge streamt - FRANZ Federer und der Grand Slam (Open End)
Livestreams vom Samstag, dem 4. Mai 2024
19:55 [L] Radlerauge streamt - Conquest-Challenge auf maximaler Schwierigkeit in Manor Lords (Open End)
Livestreams vom Sonntag, dem 5. Mai 2024
19:55 [L] Etienne streamt - RELEASE RADAR - was erscheint im Mai? !löwenanteil !scalable (Open End)
20:20 [L] Radlerauge streamt - Conquest-Challenge auf maximaler Schwierigkeit in Manor Lords (Open End)
VOD-Uploads der letzten 7 Tage
29.04.2024 17:14 Bohndesliga - HOENEẞ vs. TUCHEL: Round 1! UND: Spitzenspiel XXL Bohndesliga 31. Spieltag 2023/24
29.04.2024 18:00 Speedrundale - SILENT HILL 2 (New Game) Speedrun in 39:08 von DizzySplits
29.04.2024 19:00 Der Monatsausblick - PEN AND PAPER MIT UKE, Strategie-Gipfel uvm. Das geht im Mai
30.04.2024 09:30 Bohndesliga International - WEMBLEY Reloaded? Preview CHAMPIONS LEAGUE HALBFINALE
30.04.2024 17:30 Du bist! - Besiegen sie die PANDEMIE? PANDEMIC
30.04.2024 18:00 Game Talk - HADES II: Unterwelt der Oberklasse – Wir haben’s gespielt!
02.05.2024 15:26 Bohndesliga Extra - RANGNICK SAGT AB! Niemand will Bayern-Trainer werden!!! Reaction BOHNDESLIGA
02.05.2024 18:00 Retro Klub - BESSER ALS KINO? Videogames als Film-Sequels #2
02.05.2024 18:30 Kino+ Spezial - Was macht gute VISUAL EFFECTS & CGI aus? Talk mit VFX-Profi
02.05.2024 23:00 RBTV Home - Diese Show ist ein FIEBERTAUM! Florentin kriegt ein LIEBESLIED!
03.05.2024 16:00 Let’s Play - SOWAS spielt man nicht alle Tage!! INDIKA mit Colin & Krogi
04.05.2024 12:00 Game Two - No Rest for the Wicked, Top Spin 2K25, Sand Land Game Two #332
04.05.2024 15:00 Nerds an Herds - GARFIELDs Lasagne-Schlacht Nerds an Herds mit Eddy, Mel, Antje & Schröck
04.05.2024 16:00 Let’s Play - Wir spielen unsere LIEBSTEN STAR WARS GAMES aller Zeiten
05.05.2024 16:00 Let’s Play - Du-Du-Du-DUELL! 2 Tennis-Nerds testen TOPSPIN 2K25
Weiterführende Links
Die vollständige Liste aller Livestreams von RBTV ist unter https://rocketbeans.tv/livestreams zu finden.
Der Uploadplan mit allen Uploads dieser Woche ist hier https://rocketbeans.tv/mediathek/uploadplan.
Kurzfristige YouTube-Upload-Änderungen werden im Forum in diesem Thread kommuniziert https://forum.rocketbeans.tv/t/rbtv-youtube-uploads-channel-managment-ticke91004/9999.
Unter https://redd.it/if366o wird eine Liste von gerade streamenden Bohnen bzw. VoDs ihrer letzten Livestream-Sessions gepflegt.
Alle Folgen von MoinMoin schaut Maskedminds in diesem Thread https://redd.it/y4ih4j
2024.04.28 23:18 xBotvernor [xGov-195] Frostbits Solutions Arcpay - Frostbits Solutions
| title | Frostbits Solutions Arcpay |
|---|---|
| id | 195 |
| period | 4 |
| author | Wilder Stubbs (@WilderStubbs) |
| wilder@frostbits.solutions | |
| discussions-to | https://forum.algorand.org/t/xgov-195-arcpay/11843 |
| company_name | Frostbits Solutions |
| category | dApps |
| focus_area | Banking |
| open_source | Yes |
| funding_type | Proactive |
| amount_requested | 149000 |
| usd_equivalent | $27,848.1 (note: automated conversion) |
| delivery_date | 2024-08-31 |
| status | Final |
Abstract
Arcpay is a plug and play open-source payment processing platform to easily transact on the Algorand blockchain. Arcpay empowers businesses to receive Algorand tokens as payment simply and build advanced workflows for use cases such as community engagement through loyalty point redemption, subscription payments, e-stores, etc.Arcpay is meant to be a gateway to the Algorand ecosystem that provides a streamlined path for traditional web-based projects and removes barriers to entry through an easy to use web interface and SDK. Arcpay will support network tokens and all Algorand Standard Assets (ASAs).
Team
Our team is composed of seasoned professionals with extensive experience in blockchain technology. This background provides a robust foundation for addressing the unique challenges of integrating Web2 with Algorand Virtual Machine (AVM) technologies, ensuring Arcpay's seamless functionality across diverse digital environments.Expertise and Roles:
- Blockchain Development: Four senior software engineers, including two PhDs in computer science, bringing over a decade of combined blockchain experience.
- UI/UX Design: Specialists in creating intuitive, user-friendly interfaces that make complex functionalities accessible to non-technical users.
- Project Management: Agile and lean methodology experts ensuring that Arcpay development is responsive, on schedule, and aligned with governor expectations.
Experience with Algorand
The Frostbits Solutions team has been contributing to the Algorand ecosystem since 2021. Notably with Algogems, an Algorand platform known for its pioneering work in NFT creation and trading. We have a strong technical understanding of AVM technologies!Algogems NFT Marketplace
Present Proposal
Problem Description
Integration of Algorand technology into existing applications presents significant technical and operational challenges, hindering broader adoption and confining blockchain applications largely to niche markets. Common barriers include the need for specialized knowledge, security concerns, and integration complexities.Aligned with Algorand's vision of global decentralization, scalability, and security, Arcpay introduces a seamless gateway to the ecosystem and provides a streamlined path for businesses to transact on the blockchain. Use cases include B2B and B2C payments, loyalty point management and redemption, and removing intermediaries for improved operating margins. This will make Algorand an appealing and cost-effective choice for businesses entering the competitive Web3 ecosystem.
Solution Approach
Arcpay will bridge traditional applications and blockchain by providing:- Seamless Integration for Businesses: Comprehensive suite of APIs and a well-documented development kit for easy Algorand payment integration.
- Smart Contracts as a Service: Transparent, customizable, ready-to-deploy smart contracts for various transaction types.
- Dual Integration Modes: Magic link-based setup for non-technical users and advanced development kit integration for tailored user experiences.
Deliverable
Technical Approach
Arcpay is built on principles of flexibility and user-friendliness, with a commitment to open-source development and community collaboration. Security strategies include community-driven vulnerability assessments and periodic expert reviews if financially viable, ensuring a reliable and secure platform. The Algorand native solution will build upon and refine the Arcpay platform created for Voi Phase1 testnet.- Supports appropriate assets
- Sellable Assets
- RWAs
- No token standard, these are any goods that aren’t on chain. We provide payment processing and API integration.
- NFTs
- ASA
- ARC3
- ARC19
- ARC69
- SFTs
- ASA
- ARC3
- ARC19
- ARC69
- Buying Assets
- Tokens
- ALGO
- ASA
- Ability for user to connect their wallet
- Pera
- Defly
- Exodus
- Lute
- Views on the Arcpay Web Interface
- Sign In
- Network Switch
- Testnet
- Mainnet
- User dashboard
- Create a listing
- List of available assets
- Listing wizard
- Active listings
- List of active listings
- Manage listing (Edit, Cancel)
- Statistics
- Volume
- Revenue
- Fees
- User Settings
- Username
- Link address
- Social links
- Secondary market settings
- Fee rate
- API subscription page
- Free
- Paid
- Purchase
- Buy Now
- RWAs
- NFTs
- SFTs
- Bid
- NFTs
- SFTs
- Supported sale mechanisms facilitated by smart contracts.
- Fixed-price sale
- ALGO for RWAs
- ASA for RWAs
- ALGO for ASA
- ASA for ASA
- Auctions
- English
- ALGO for ASA
- ASA for ASA
- Dutch
- ALGO for ASA
- ASA for ASA
- Link to assets on the block explorer
- Allo
- Pera Explorer
- Deployed and working on
- Algorand
- Testnet
- Mainnet
Concerns & Risks
Concerns Mitigation Strategies---------------------------------
Technical Challenges Incremental Deployment: Roll out features in stages to manage complexity and allow for focused testing and optimization at each step.
Community Beta Testing: Prior to official release, conduct extensive beta testing with community members to ensure real-world applicability and robustness.
Bugs and Broken Features Ongoing Maintenance Post-Launch: Continue to address and rectify any issues that arise post-launch on the mainnet, ensuring the platform remains reliable and secure.
Adoption Rates Partnerships: Form strategic partnerships with key players within the Algorand ecosystem to leverage their networks and gain credibility.
Hosting Sustainability Revenue Model Implementation: Develop and implement a clear revenue model to support long-term hosting and operational costs.
Performance Monitoring: Regularly review performance metrics to ensure that hosting remains financially viable and adjust strategies as needed.
Documentation and Community Support Documentation: Develop comprehensive, easy-to-understand user and developer documentation.
Community Channels: Establish and maintain active community support channels, including forums, live chat support through Telegram, X, and Discord.
Feedback Loops: Implement structured feedback loops to continuously improve documentation and support based on user input.
Ongoing Maintenance A 4-week review and validation phase per milestone launch, followed by ongoing maintenance, ensures platform reliability.
Future Blueprint
Project Longevity
Designed for sustained growth, Arcpay will evolve with blockchain advancements and community feedback. Supported on both the Algorand testnet and mainnet, our platform aims for long-term operational sustainability through a clear revenue model. Our commitment extends to maintaining the platform for at least one year after final delivery, with intentions to continue as long as it remains economically feasible.Project Timeline
- Development Kickoff: Immediately after successful voting, targeted to start smart contract development by June 3rd.
- Milestone 1 - MVP Release: Core functionalities within four weeks.
- Milestone 2 - Enhanced Features: Introduction of auction systems by the sixth week.
- Milestone 3 - Final Delivery: Full deployment readiness by the eighth week.
Milestones
Milestone ETA Scope-----------------------
Milestone 1 - MVP 4 weeks - ASA to ASA sale contract
- End-to-end UI to create sale and interact with contract (Sign In, User dashboard to create, edit, and list NFTs and payment modal)
- Link to assets
- Secondary market sales listings and settings
- Integration through direct links
- Development kit to interact with the listings
- Documentation
Milestone 2 6 weeks - ALGO to ASA sale contract
- ASA to ASA English Auction contract
- ASA to ASA Dutch Auction contract
- ALGO to ASA English Auction contract
- ALGO to ASA Dutch Auction contract
- Secondary market auctions listings
- Updated UI for Auctions
- Updated Development kit for Auctions
- Updated documentation
Milestone 3 - Final Delivery 8 weeks - ALGO to RWAs sale contract
- ASA to RWAs sale contract
- User dashboard with statistics and settings
- API Subscription page
- Updated UI for RWAs sale
- Updated Development kit for RWAs sale
- Network switch
- Updated documentation
Benefits for the community
Expected Impact & Outcomes for the Algorand Community
- Ecosystem Growth: Simplifies integration for businesses, promoting Algorand ecosystem growth.
- Broadening Accessibility: Bridges traditional and decentralized economies, revolutionizing B2B and B2C transactions on Algorand.
- Analytics: Provides businesses sophisticated tools to refine strategies and align offerings with market demands.
- Strategic Partnerships: Enhances utility and liquidity of tokenized assets with major Algorand projects. This includes Cosmic Champs, Algo Leagues, Flipping Algos, and the list grows.
Define Success
Success for Arcpay will be defined by the adoption rate among businesses and P2P users, the volume of transactions processed through the smart contracts, and positive community feedback regarding its impact on the ease of integration.We envision Arcpay’s success playing out in two sequential stages:
- Adoption by top Algorand players such as top NFT projects, Wallets, and existing dapps.
- Expansion to traditional businesses and non-Algorand native Web3 projects.
Additional information
Contact Information
This proposal is supported by Frostbits Solutions, a Canadian company specialized in custom, cutting-edge software, that leverages decentralized networks to facilitate rapid, secure, and cost-effective exchanges of digital goods.Website: frostbits.solutions
Email: wilder@frostbits.solutions
Twitter: @WilderStubbs
Discord: Wilder
Github Links
Proposal on GithubConversation and changes can be found in the top comments.
2024.04.28 16:40 Lucacg00 Any bad experiences with this 2008 Corsair TX 750W? It's for a Socket A PC build
Very old socket I know, but my Antec TPT 550 died. Bad caps.
I need a PSU that can power both my 9800XT (1xFDD) and my Molex fan daisy chain in my Antec Dragon 2004 gun metal case (2xMolex needed). The cable needs to be long.
This PSU is perfect for me. I just want to know if it's reliable.
specs:
AMD Athlon XP 3200+
MSI K7N2 Delta2 nF2 Ultra 400 MCP RAID
Radeon 9800XT XXL (HIS)
2048MB DDR dual channel DDR-400
80GB WD SATA drive
Pioneer DVD RW IDE drive
submitted by Lucacg00 to buildapc [link] [comments]
I need a PSU that can power both my 9800XT (1xFDD) and my Molex fan daisy chain in my Antec Dragon 2004 gun metal case (2xMolex needed). The cable needs to be long.
This PSU is perfect for me. I just want to know if it's reliable.
specs:
AMD Athlon XP 3200+
MSI K7N2 Delta2 nF2 Ultra 400 MCP RAID
Radeon 9800XT XXL (HIS)
2048MB DDR dual channel DDR-400
80GB WD SATA drive
Pioneer DVD RW IDE drive