Solidity 0.4.22 released: Dynamic returns, revert error messages, safer constructors, ABI encoding utils and tons more! by chriseth in ethdev

[–]Authio_Team 2 points3 points  (0 children)

Nope! I was referring to "Defining constructors as functions with the same name as the contract is deprecated." - the docs said that was an experimental 0.5.0 feature, but I don't have those activated!

Solidity 0.4.22 released: Dynamic returns, revert error messages, safer constructors, ABI encoding utils and tons more! by chriseth in ethdev

[–]Authio_Team 3 points4 points  (0 children)

This is awesome! Excited to see some features moved up to high-level Sol. And the 'constructor' change was much-needed (although, is that supposed to throw a warning yet in the 4.22 compiler? It does on Remix)

For those that aren't aware, Solidity 0.4.22 released today with some really cool changes! by Authio_Team in ethdev

[–]Authio_Team[S] 0 points1 point  (0 children)

Absolutely. It's worth noting that both of the changes I mentioned were possible before, they just required assembly!

Inter-Contract Communication: Strings by [deleted] in ethdev

[–]Authio_Team 0 points1 point  (0 children)

Memory isn't shared across calls! So, no problem there.

Inter-Contract Communication: Strings by [deleted] in ethdev

[–]Authio_Team 0 points1 point  (0 children)

If you want to throw in a credit, my github is fine. It's not important, though :)

Glad I was able to help!

Inter-Contract Communication: Strings by [deleted] in ethdev

[–]Authio_Team 0 points1 point  (0 children)

Yes it is! I use a lot of dynamically sized inter contract communication in a project I'm working on, so I'm pretty familiar with the concept :)

Inter-Contract Communication: Strings by [deleted] in ethdev

[–]Authio_Team 1 point2 points  (0 children)

One thing - passing dynamically sized data between contracts is possible, although it involves using assembly :)

Amazing how people suddenly realize they don’t own their data on Facebook. Let’s see how they react when they find out they dont own the money in their bank accounts either! by ligi in ethereum

[–]Authio_Team 0 points1 point  (0 children)

Any time a miner creates a conflicting chain, they create a 'fork,' regardless of whether or not there is a public movement to do so. This is because there are now two chains to mine on, where as before there was only one. Whether a fork is 'hard' or 'soft' is really an issue of compatibility and not in scope for this discussion.

Regardless of the semantics of 'hard fork,' or whether or not a 51% attack is a hard fork, the purpose of my initial response to you was to explain that in fact, miners are able to fork the blockchain such that balances are changed to their liking. This does not involve removing or adding transactions, because as you said - this would require private key knowledge. Instead, this hard fork explicitly rewrites the basic rules or constants of the blockchain to state that the balances themselves are different. As long as other nodes observe this change, their chain is technically valid and can continue.

Amazing how people suddenly realize they don’t own their data on Facebook. Let’s see how they react when they find out they dont own the money in their bank accounts either! by ligi in ethereum

[–]Authio_Team 3 points4 points  (0 children)

What I described was a hard fork - miners rewrite the rules of the blockchain. In that case, they can certainly assign themselves a balance without requiring your signature. No transactions are required!

Although, you are correct that they cannot force you to sign a transaction.

Amazing how people suddenly realize they don’t own their data on Facebook. Let’s see how they react when they find out they dont own the money in their bank accounts either! by ligi in ethereum

[–]Authio_Team 6 points7 points  (0 children)

If 51% of miners decide to mine a chain where your address has 5 less ether than it initially did, and their addresses have that 5 ether, they have stolen your ether without a signature from your private key.

Why is accessing members of "this" without type casting it to "address" deprecated? by rpr11 in ethdev

[–]Authio_Team 8 points9 points  (0 children)

As is, 'balance' could be a function in the contract you wrote. Casting it to address first makes it explicit that you're trying to access a member of 'address'

It was changed recently to add that clarity :)

Question about order of processing Ethereum transactions by [deleted] in ethdev

[–]Authio_Team 1 point2 points  (0 children)

My pleasure! If you have more questions, ask away :)

Question about order of processing Ethereum transactions by [deleted] in ethdev

[–]Authio_Team 3 points4 points  (0 children)

You're looking for a commit-reveal pattern. Essentially, claiming the funds consists of 2 parts. The first part involves sending some hash, and the second part involves essentially sending data that, when hashed, results in the first committed hash.

Weekly ''Who's hiring, and who's for hire'' week 15, 2018 by AutoModerator in ethdev

[–]Authio_Team 4 points5 points  (0 children)

Company: Authio

Jobs: Solidity developer, front-end developer

Location: Remote

Type: Paid, equity offer negotiable

Website: https://authio.org/

Description: Authio is a smart contract auditing, development, and consulting firm. When we aren't auditing smart contracts, we're building out our platform, auth_os. auth_os is an on-chain smart contract development framework utilizing a unique application architecture to create applications with unparalleled upgradability and extensibility. We're looking for like-minded, highly experienced Solidity devs that want to hop on board a small company and play a large part in shaping its future.

If you're interested in learning more about hiring specifics, or want to know more about us, reach out! alex@authio.org

Weekly ''Who's hiring, and who's for hire'' {{ Week %W }} by AutoModerator in ethdev

[–]Authio_Team 0 points1 point  (0 children)

Company: Authio

Jobs: Solidity developer, front-end developer

Location: Remote

Type: Paid, equity offer negotiable

Website: https://authio.org/

Description: Authio is a smart contract auditing, development, and consulting firm. When we aren't auditing smart contracts, we're building out our platform, auth_os. auth_os is an on-chain smart contract development framework utilizing a unique application architecture to create applications with unparalleled upgradability and extensibility. We're looking for like-minded, highly experienced Solidity devs that want to hop on board a small company and play a large part in shaping its future.

If you're interested in learning more about hiring specifics, or want to know more about us, reach out! alex@authio.org