Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shilch
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
shilch
5y ago
Here you go: https://shilch.me/bitcoin-turing-complete/
2.
▲
by
shilch
5y ago
I might write an article that explains it (if I find the time to do so). The thread form of back and forth is fruitless since it appears that we don't have a common understanding of what makes bitcoin turing complete. Let me know how
3.
▲
by
shilch
5y ago
> because bitcoin script is not turing-complete This is not what the article claims to show. It shows that the system bitcoin is turing complete. Added to this, having an "external driver" and the system being turing-complete a
4.
▲
by
shilch
5y ago
The proof in the article is not about unrolling. Whatever I read regarding "covenant" requires a protocol change. Independent of who described the underlying technique first, this doesn't invalidate the proof.
5.
▲
by
shilch
5y ago
The loop unrolling is an implementation detail. As I have written somewhere else: You could as well have put a large if-else there to do the transition table lookup. In the GoL example, one generation update is performed in every transact
6.
▲
by
shilch
5y ago
This is not at all what this article describes. You're making the same mistake as truth_machine does: The loop unrolling is not part of the proof but just an implementation detail for the transition lookup; it could as well have been a
7.
▲
by
shilch
5y ago
Then you either misunderstand or (intentionally?) misrepresent the article. The `loop` construct you're talking about has nothing to do with the author's proof, and neither does it "essentially use bitcoin blockchain as a dat
8.
▲
by
shilch
5y ago
In Ethereum, the caller specifies the gas amount beforehand to ensure that the execution finishes. In the presented bitcoin-based solution, the caller prepares the transactions beforehand that finish the execution; it then publishes the tra
9.
▲
by
shilch
5y ago
I don't know what you're up to; your account is 30min old, was created just for commenting on this post, you appear to be very aware of this project and your comments show that you didn't understand the solution presented in
10.
▲
by
shilch
5y ago
These are two separate things. The `loop` construction / function or whatever it is called in the sCrypt language is a compile-time loop. That is, the body gets unrolled N times (8 in this example). It's just an implementation d
11.
▲
by
shilch
5y ago
The presented solution does *not* loop inside bitcoin script itself, as you suggest, but outside whereby bitcoin transactions perform the state transfer. The machine runs for as long as someone pays for it (or it goes into accepting state)
12.
▲
by
shilch
5y ago
I just wrote the comment and noticed that the scripting limits on BCH are actually a network rule and are not miner-configurable. So my statement that "it could also work on BCH if some default limits were lifted" is only correct
13.
▲
by
shilch
5y ago
> BSV and Bitcoin (BTC) are incompatible protocols Both implementations have a large intersection. Dogecoin, Litecoin and Dash also use the bitcoin protocol and should also work. > Sure, it can be added to BTC The presented solution d
14.
▲
by
shilch
5y ago
I was aware of xhliu's work before. It's actually a big thing because Ethereum was created with the assumption that bitcoin's scripting language does not allow for state transfers (stateful contracts) and turing-complete comp
15.
▲
by
shilch
5y ago
The solution presented in the article uses the bitcoin protocol. BSV is just one implementation of that. It could also work on BCH if some default limits were lifted, and (theoretically, not economically) possible on BTC.
16.
▲
by
shilch
5y ago
MacOS doesn't have jails as FreeBSD does. But they are using some kind of isolation for Mac applications, so they can not see data of other applications.
17.
▲
by
shilch
6y ago
(A port of) Visual Studio Code is available for FreeBSD (using it myself); `pkg install vscode`. If you would like to use docker, you could run a Linux distro in a virtual machine with docker daemon and configure your host docker command
18.
▲
by
shilch
7y ago
Like computer scientist, they think binary: Either it's secure, or it's not. In reality there's a spectrum where you also have "good enough".
19.
▲
by
shilch
7y ago
Clang also does some crazy-good SIMD optimizations if you set -march=native. But I think the Rust compiler is based on LLVM as well, right?
20.
▲
by
shilch
7y ago
I don't think that "Peer-to-Peer" in the whitepaper's title ("Bitcoin: A Peer-to-Peer Electronic Cash System") refers to the network structure being p2p - and that's probably also not what most people mean
21.
▲
by
shilch
7y ago
I'm not all too familiar with the history of IP and TCP but my point still stands. Protocols aren't build because the underlying protocol doesn't scale in term of throughput, it's for the opposite reason that they scale
22.
▲
by
shilch
7y ago
TCP wasn't build on IP because it wasn't scalable. It was build on it because it was. But that aside, calling Lightning on BTC a second-layer is a bit misleading: Lightning data is not encapsulated in BTC data, more like the oth
23.
▲
by
shilch
7y ago
> Do you mean "the GUI shows 0-conf transactions as pending? It's not just GUI but also a miner policy which can break the use of BTC as cash - as it was originally intended. > And why does adding Segwit make it "not bi
24.
▲
by
shilch
7y ago
BTC hard forked twice (or thrice if you count the one accidental hard fork) and soft forked a dozens of times. Claiming that BTC is the "main chain" is misleading. The main chain is dead for years; run the original bitcoin client,
25.
▲
by
shilch
7y ago
It uses the Bitcoin protocol and operates on the Bitcoin SV network (notice the space) by default.
26.
▲
by
shilch
7y ago
It uses "Bitcoin" to refer to the protocol, not the BTC network. People fought about the name "Bitcoin" for ages and everybody has their own opinion about this topic. The network that you refer to as Bitcoin has forked s
27.
▲
by
shilch
7y ago
In theory it could work on BTC or BCH. Bottle relies on large OP_RETURN which is a miner-adjustable limit, not consensus. But in practice you (1) would need to find a miner to do this. (2) could only put in 1MB of data on BTC. (3) wou
28.
▲
by
shilch
7y ago
It's all about the incentives. What is the incentive in IPFS to keep data? If offering it to clients earns you money, what is the incentive to distribute it to competing peers? The blockchain is the solution: A miner must distribute th
29.
▲
by
shilch
7y ago
Good summary. > Bitcoin developers later introduced opcode "OP_RETURN", which is seen as a standard and less-evil way to post data. This is not true and an error in the Mastering Bitcoin book. OP_RETURN was introduced by Satosh
30.
▲
by
shilch
7y ago
I guess the word "Bitcoin" used here refers to the protocol that the browser builds on, and not the chain commonly known as Bitcoin which has BTC as base asset. Bottle is not limited to BSV but could as well be run on other chains
More ›