Ecosyste.ms: Timeline
Browse the timeline of over 8.13 Billion events for every public repo on GitHub, all the way back to 2015. Data updated hourly from GH Archive.
MightOfOaks pushed 1 commit to serkan/sg721-v1-update public-awesome/launchpad
- Update rust version for CI f218096
MightOfOaks created a review comment on a pull request on public-awesome/launchpad
The contract will be used for new open edition collections onwards without any migrations. It could cause indexing errors though if not accounted for.
MightOfOaks created a review comment on a pull request on public-awesome/launchpad
`mintable_num_tokens` is only Some when there is no end time defined (as per instantiation), so the minting cannot be time limited in this case.
MightOfOaks created a review comment on a pull request on public-awesome/launchpad
The reasoning was that the upwards updates are the risky ones that may cause traders to lose money if the change is too steep.
MightOfOaks created a review comment on a pull request on public-awesome/launchpad
Earlier the code was in sync with a v2 update that we abandoned and was never deployed on chain. So, the v1 contracts that are currently on chain do not have an `updated_at` attribute in their Coll...
tasiov created a review comment on a pull request on public-awesome/launchpad
curious if this will cause errors on read
tasiov created a review comment on a pull request on public-awesome/launchpad
so what if it's ended but not sold out?
tasiov created a review comment on a pull request on public-awesome/launchpad
what if `share < old_royalty_info.share`
tasiov created a review comment on a pull request on public-awesome/launchpad
just want to check with @MightOfOaks to make sure this won't break on read
tasiov created a review comment on a pull request on public-awesome/launchpad
this will be a PITA to update, but this may be how we must do it for now
MightOfOaks pushed 1 commit to serkan/sg721-v1-update public-awesome/launchpad
- Update parameter name for sg721-updatable/migrate() 8bea759