You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
need to sort out simulator setup and environmental issues; have an easy way and instructions for running completely separately from mainnet etc install
chialisp tutorial perhaps should use or have an option for using simulator. i would compare this to developing using regtest on Bitcoin, which is easier and faster than trying w/ Bitcoin mainnet
--
process should really be friendly to the following environments, which should be tested:
dev already having full mainnet node running w/ packaged install
with previous versions installed and hard upgraded over
totally separate dev environment for testnet and simulator; no overlapping things that can screw things up, separate keychains
default tutorial and instructions should be based on this even if it means longer commands to pass config dirs etc
should match expectations of someone coming from bitcoin dev or eth dev w/ hardhat/truffle etc, except when there's major reason not to
default dev tutorial instructions should be built around simulator rather than testnet
Version
2.0.0
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
Hi, fyi, i created a new 'chiatest' o/s user, added it to sudoers, and was able to do a clean simulator setup and configuration that way. This could be mentioned in docs as one option.
What happened?
Took another stab at Chialisp yesterday briefly
Profile: a dev on a laptop who's already running a full mainnet node
Details:
https://twitter.com/adrianscottcom/status/1700829090251420119
Takeaways:
--
process should really be friendly to the following environments, which should be tested:
Version
2.0.0
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: