Nikolai Mushegian

sig collision?

2

Looks like ANY trick is fine for src/dest, but is there some fuckery that could happen with a malicious function signature `bytes4(uint32(-1))`? @dbrock

the first word is the length in a dynamic array

fun aliases

4

Let's leave the regular names bc backwards compatability and this is good normie bait But let's still have good words `load` -> `cock` ->`fire` consistent with `fire` from ds-clock

could rename the file in the actual ds-token, idc

Improve the readme by rearranging and deleting text and adding better examples NOT by adding badges and other bullshit

This is actually super good https://github.com/nmushegian/jams

Is it because I'm an NSA agent lowering your safety standards, no, I just think it would be cool to fit the whole CID into one ethereum storage slot

Based on our current usage it seems like we can just have a single pure `build` function. (We should also still have stateful builder pattern). ``` const pack = dpack.build({...

checklist issue for dpack-1 validation conditions

6

isValidType and isValidObject - [ ] typenames are mixedcase alphanumeric plus underscores - [ ] typenames start with capital letter isValidObject - [ ] objectnames are mixedcase alphanumeric plus underscores...