Skip to content

/mist

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update solc to 0.4.18 #3274

Merged
merged 1 commit into from Nov 13, 2017

Conversation

@wjmelements
Copy link
Contributor

wjmelements commented Nov 11, 2017

I'm eager for 0.4.18 since it has the memory byte array fix.
@wjmelements
update solc
Loading status checks…
a071c0d
@wjmelements

This comment has been minimized.

Sign in to view
Copy link
Contributor Author

wjmelements commented Nov 12, 2017

Tested via Deploy contract; successfully deployed a 0.4.18 contract to Rinkeby.
@evertonfraga
evertonfraga approved these changes Nov 13, 2017
View changes
@evertonfraga evertonfraga reopened this Nov 13, 2017
@evertonfraga

This comment has been minimized.

Sign in to view
Copy link
Member

evertonfraga commented Nov 13, 2017

I've closed and reopened this PR to trigger Travis build service. Once it gives the green flag, I'll merge.
@evertonfraga evertonfraga merged commit b986c1b into ethereum:develop Nov 13, 2017
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@savao

This comment has been minimized.

Sign in to view
Copy link

savao commented Jan 15, 2018

Hello.
Please specify what compiler version is used now in the Mist? I can't verify the contract, which was deployed through the Mist in Etherscan.io. I'm tried different version of 0.4.18 compiler, of which it is possible to choose, but verification every time gives an error:
"Sorry!
We encountered an unexpected error.
Please try back again shortly"
Can't understand how do I can verify a contract.
Set optimize to No, Run to 0, put ABI which gave me a Mist. But still take this error.
@lock

This comment has been minimized.

Sign in to view
Copy link

lock bot commented Apr 15, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
@lock lock bot locked and limited conversation to collaborators Apr 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@evertonfraga evertonfraga

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@wjmelements @evertonfraga @savao
You can’t perform that action at this time.