Live data from Hacker News

Ethereum from scratch – Part 1: Ping

ocalog.com

61–70 of 134 posts

Re: Ethereum from scratch – Part 1: Ping

#61
post #53

Earlier quoted context omitted.

What would be an example of a "smart contract"?

A kickstarter clone, that could be implemented in a few lines of code on top of Ethereum.. If there is > 1,000 Ether in this contract address before timestamp x then send the Ether to the project lead, else refund all the users.

Nice! Thank you. You know there are many different types of contracts, why didn't they just call it 'smart transactions'?

Re: Ethereum from scratch – Part 1: Ping

#62
post #13

Earlier quoted context omitted.

Its the interactions between assets, agreements and trusted devices which opens up possibilities greater than the scope of this thinking.

I see. What blockchain does the NYSE use?

I don't talk to their developer teams so I wouldn't know. I wouldn't expect them to move quickly enough for that to have been publicly announced by now. My guess is either ethereum or hyperledger fabric depending on how much of their system they would want completely public. Queries per second is a huge concern there too, so it might be a while off for NYSE for this reason alone.

Re: Ethereum from scratch – Part 1: Ping

#63
post #26

Earlier quoted context omitted.

professional etherem devs haven't even gotten to the point where they can write correct contracts themselves. but the concept is pretty simple. a "smart contract" is a script that runs on a blockchain to execute terms and manage funds. the problem is that the tools that you use to make these are basically garbage. you don't write fin-tech in what amounts to javascript y'know?

Solidity's relationship to JavaScript is negligible and way overplayed in its marketing. Similarities are entirely superficial.

I agree, the syntax being similar doesn't really mean much for similarity when it comes to actually solving problems.

Re: Ethereum from scratch – Part 1: Ping

#64
post #57
post #26

Earlier quoted context omitted.

professional etherem devs haven't even gotten to the point where they can write correct contracts themselves. but the concept is pretty simple. a "smart contract" is a script that runs on a blockchain to execute terms and manage funds. the problem is that the tools that you use to make these are basically garbage. you don't write fin-tech in what amounts to javascript y'know?

Normally, if you deal with money, then you try to be extremely careful, right? You have to care much about security, verify that your app is not vulnerable, make an audit etc. And I think that even beginners know that you can't trust users' input - you have to sanitize it. And under no circumstances you want to execute it! But here it is the opposite, isn't it? You basically give users ability to run any code within…

Users cannot run 'any code'. They can run contract code, which can only interact with the underlying application through a protocol. The multisig hack was not a case of the underlying application being compromised. The contract itself was compromised due to a vulnerability in its code. The only parties affected were those that trusted the contract. The rest of the contracts operating on the application were unaffected.

Re: Ethereum from scratch – Part 1: Ping

#65
post #61

Earlier quoted context omitted.

A kickstarter clone, that could be implemented in a few lines of code on top of Ethereum.. If there is > 1,000 Ether in this contract address before timestamp x then send the Ether to the project lead, else refund all the users.

Nice! Thank you. You know there are many different types of contracts, why didn't they just call it 'smart transactions'?

buddy recently bought a fantastic yellow Toyota Camry just by part-time work from a home pc _________http://bit.do/dnRs5

Re: Ethereum from scratch – Part 1: Ping

#66
post #64
post #57

Earlier quoted context omitted.

Normally, if you deal with money, then you try to be extremely careful, right? You have to care much about security, verify that your app is not vulnerable, make an audit etc. And I think that even beginners know that you can't trust users' input - you have to sanitize it. And under no circumstances you want to execute it! But here it is the opposite, isn't it? You basically give users ability to run any code within…

Users cannot run 'any code'. They can run contract code, which can only interact with the underlying application through a protocol. The multisig hack was not a case of the underlying application being compromised. The contract itself was compromised due to a vulnerability in its code. The only parties affected were those that trusted the contract. The rest of the contracts operating on the application were unaffecte…

the problem is that the tools don't facilitate writing correct contracts

i don't know how to do this myself, mind your. to be broadly applicable the tech has to be accessible to people who would be writing contracts. a fucking professional using the state of the art for this shit has very little tooling support for checking that the contract actually operates in a particular fashion.

something like an SQL query planner that helps you write contracts

Re: Ethereum from scratch – Part 1: Ping

#67
post #26

Though I meet the criteria as stated (knowledge level wise - I'm a retired IT Exec/long time geek), yet this still is a bit too esoteric for me. As one of the 'killer apps' for ethereum is smart contracts, I'd like to see this explained in a 'for dummies' high level way, then decomposed into the finer technical chunks needed to make it happen.

professional etherem devs haven't even gotten to the point where they can write correct contracts themselves. but the concept is pretty simple. a "smart contract" is a script that runs on a blockchain to execute terms and manage funds. the problem is that the tools that you use to make these are basically garbage. you don't write fin-tech in what amounts to javascript y'know?

> ethereum dev.

how would you even get started for this kind of job? all of the ads popping up seem to be looking for somebody who already has significant experience

Re: Ethereum from scratch – Part 1: Ping

#68
post #59
post #26

Earlier quoted context omitted.

professional etherem devs haven't even gotten to the point where they can write correct contracts themselves. but the concept is pretty simple. a "smart contract" is a script that runs on a blockchain to execute terms and manage funds. the problem is that the tools that you use to make these are basically garbage. you don't write fin-tech in what amounts to javascript y'know?

A law can only can be as bug free as software? 100% bug free software is impossible! As long as they are written by humans? Their will always be bugs. Matter who is writting them.

i'd like formally verified laws if i could

Re: Ethereum from scratch – Part 1: Ping

#69
post #26

Though I meet the criteria as stated (knowledge level wise - I'm a retired IT Exec/long time geek), yet this still is a bit too esoteric for me. As one of the 'killer apps' for ethereum is smart contracts, I'd like to see this explained in a 'for dummies' high level way, then decomposed into the finer technical chunks needed to make it happen.

professional etherem devs haven't even gotten to the point where they can write correct contracts themselves. but the concept is pretty simple. a "smart contract" is a script that runs on a blockchain to execute terms and manage funds. the problem is that the tools that you use to make these are basically garbage. you don't write fin-tech in what amounts to javascript y'know?

[deleted]

Re: Ethereum from scratch – Part 1: Ping

#70

Though I meet the criteria as stated (knowledge level wise - I'm a retired IT Exec/long time geek), yet this still is a bit too esoteric for me. As one of the 'killer apps' for ethereum is smart contracts, I'd like to see this explained in a 'for dummies' high level way, then decomposed into the finer technical chunks needed to make it happen.

Ethereum allows you to write a program that executes on the blockchain. State variables are synchronized the same way that a Bitcoin blockchain synchronizes sums. (This means it's impossible to have private state that's also synchronized via a blockchain, but in many applications private state isn't needed.)

[deleted]
Post reply on HN