cerc-io/stack-orchestrator
16
1
Fork 1
Code Issues 88 Pull Requests 11 Actions Packages Projects Releases 442 Wiki Activity

Facilitate deploying EVM contract bytecode #217

New Issue
Closed
opened 2023-03-11 21:25:45 +00:00 by dboreham · 2 comments
dboreham commented 2023-03-11 21:25:45 +00:00
Owner
Copy Link

Given a set of .bin (ASCII-encoded HEX EVM bytecode) files, deploy to a fixturenet-eth with minimal fuss and confusion.

Given a set of `.bin` (ASCII-encoded HEX EVM bytecode) files, deploy to a fixturenet-eth with minimal fuss and confusion.
dboreham commented 2023-03-11 21:27:51 +00:00
Author
Owner
Copy Link

This works with some manual steps at present:

You can put the .bin files in the directory ./app/data/compose/foundry/workspace then run a command like this to deploy:

$ laconic-so --stack fixturenet-eth deploy exec foundry "cast send --gas-limit 10000000 --private-key 888814df89c4358d7ddb3fa4b021
3e7331239a80e1f013eaa7b2deca2a41a218 --create --code-file /workspace/ERC20.bin"

blockHash               0x84b3b64616063166b013842ac54f7972ad7b6ee5d5386143cb68c4e2f73cd4cc
blockNumber             716
contractAddress         0xCf5207018766587b8cBad4B8B1a1a38c225ebA7A
cumulativeGasUsed       147667
effectiveGasPrice       3000000007
gasUsed                 147667
logs                    []
logsBloom               0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
root
status                  0
transactionHash         0xf434a6edf4f698db488fa01eafb8c706bfbda4cb234017d29d52f8a679c2aa5b
transactionIndex        0
type                    2

This requires knowing the magic private key and is missing some sort of automatic packaging scheme to go from to .

This works with some manual steps at present: You can put the `.bin` files in the directory `./app/data/compose/foundry/workspace` then run a command like this to deploy: ``` $ laconic-so --stack fixturenet-eth deploy exec foundry "cast send --gas-limit 10000000 --private-key 888814df89c4358d7ddb3fa4b021 3e7331239a80e1f013eaa7b2deca2a41a218 --create --code-file /workspace/ERC20.bin" blockHash 0x84b3b64616063166b013842ac54f7972ad7b6ee5d5386143cb68c4e2f73cd4cc blockNumber 716 contractAddress 0xCf5207018766587b8cBad4B8B1a1a38c225ebA7A cumulativeGasUsed 147667 effectiveGasPrice 3000000007 gasUsed 147667 logs [] logsBloom 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 root status 0 transactionHash 0xf434a6edf4f698db488fa01eafb8c706bfbda4cb234017d29d52f8a679c2aa5b transactionIndex 0 type 2 ``` This requires knowing the magic private key and is missing some sort of automatic packaging scheme to go from <repo-with-solidity> to <bin files>.
dboreham commented 2023-03-28 15:58:36 +00:00
Author
Owner
Copy Link

Calling this done since a contract can now be deployed with cast send.

Calling this done since a contract can now be deployed with `cast send`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
feature

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
in progress

   
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#217
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?