CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644775707601989?thread_ts=1644775707.601989&cid=C5131HKFX

https://t.me/CSW_Slack/3991

What I will state very simply and make sure that people understand is that bitcoin is a legal contract system. There is a unilateral contract that pays miners. Those miners or nodes are paid money to conduct a service. If they don’t do the service, if they attempt to change the protocol or operate outside of the legal boundaries or think that they can do things that are not within the protocol, they are liable for any damages in contract and tort.

Double spend protection is not technical. Like most aspects of Bitcoin, it is a technical constraint linked to an economic condition. In this, if a node, any node does not relay a single transaction and this ends in a double spend, that node is 100% liable for the direct loss and ALL costs. Without execption.

If a 100 millin USD transaction is made with ZERO fees and your node does not relay it, and ANY node connected to you fails to get this and sees a double spend, your node is liable for the loss. The recipient of the double spend and come to you and you will need to pay.

That is how relay fees work

If you have one, you have a HUGE liability

UNLIMITED

Liability

to save SMALL amounts of money

Basically, the entire concept of a relay fee is a stupid idea

And, any miner not forwarding EVERY TX is a dumb fuck who wants to be put out of business.

You do not need to mine a zero fee tx... YOU DO NEED TO FORWARD it as a miner

Not mining and puttin git in a block is separate to not forwarding

Nodes Relay

They are Paid for this - they have a subsidy

CSW
Feb 23, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1645622968111309?thread_ts=1645622968.111309&cid=C5131HKFX

https://t.me/CSW_Slack/4060

"The software was developed with the aim to allow miners to freeze coins which are determined by valid legal process to be lost or stolen, such that they may be returned to their rightful owner."

https://bitcoinassociation.net/bitcoin-association-for-bsv-tulip-trading-ltd-settlement-statement-and-faq/

The law applied to Bitcoin when it was issued and launched in 2009. I studied UK Law for my LLM thesis which was submitted in 2007. I did this to ensure that Bitcoin was within the legal frameworks.

Electronic cash was regulated in 1996.

CSW
jun 17, 2022
https://www.linkedin.com/posts/craigswright_regulation-crypto-blockchain-activity-6943525509939003392-IFyN?

The Impact of Internet Intermediary Liability
89 Pages
Date Written: April 17, 2008
Dr Craig S Wright
nChain
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2953929

The Evolution of the Constitution
By Craig Wright
29 Jun 2022
Law & Regulation

https://craigwright.net/blog/law-regulation/the-evolution-of-the-constitution/

NOTICE OF OWNERSHIP
https://www.youtube.com/watch?v=shVA-7Z7YvE
BitcoinSV TV - 01/Jul/2022
--
by @BSVVideosBot / @BSVBots

Min: 2h26:07
Craig was never convicted 2004

Craig Wright Full Testimony: Hodlonaut v Craig Wright - Day 3
14 sept 2022
This is the full video from Craig Wright's testimony on day 3 of the Hodlonaut v Craig Wright trial on September 14th, 2022.
https://www.youtube.com/watch?v=_zkweFcpQMs

A confiscation transaction is identified by the first transaction output being an OP_RETURN output which adopts the confiscation transaction protocol (See https://github.com/bitcoin-sv-specs/protocol/tree/master/updates) and contains a reference to identify the related ConfiscationOrder document. The complete Court order document is not embedded in the OP_RETURN data of the confiscation transaction because not all blockchains support a large payload. For example, the default data carrier size on BTC is 80 bytes.

Highlights of the feature

Introduces support for confiscation transactions, which when explicitly whitelisted can spend consensus frozen TXOs without providing unlocking scripts.
Outputs of a confiscation transaction can only be spent when they mature (CONFISCATION_MATURITY = 1000 blocks), similar to coinbase outputs.
A flag to indicate that an output was created by a confiscation transaction is stored in the UTXO database and block undo files by the 32nd bit in the existing value that stores height + is_coinbase and is serialized as the VARINT data type. If this flag is set to 0, the serialized value is exactly the same as before, which makes it backward compatible. However, if this flag is set to 1, the serialized value cannot be read by the previous versions of the node because it no longer fits in a 32 bit integer as was expected in previous versions. This is detected as a serialization exception, which results in stopping the node.
Downgrading to the previous versions of the node is only possible if all of the following is true:
There are no confiscation transactions in blocks on the active chain.
If there are, these blocks will be incorrectly detected as invalid or the node will not work correctly due to the UTXO database incompatibilities.
There are no whitelisted confiscation transactions in the database.
If there are, their records in the database will result in an incorrect handling of consensus frozen TXOs.
Before downgrading all whitelisted transactions should be removed from the database by calling clearConfiscationWhitelist RPC function.