lavalamp

Security fixes for contracts using Solidity v0.7?

1

**🧐 Motivation** Hi there! I'm currently trying to address some security vulnerabilities in a repository that uses the `contracts` library. Unfortunately the codebase in question requires Solidity version `0.7` and...

Ensure all the addresses that have already been discovered are available via the web portal.

Concurrent map write exception

1

goroutine 623552856 [running]: runtime.throw(0xa8fe96, 0x26) /snap/go/3739/src/runtime/panic.go:617 +0x72 fp=0xc000058b78 sp=0xc000058b48 pc=0x42ecf2 runtime.mapiternext(0xc000058d60) /snap/go/3739/src/runtime/map.go:860 +0x597 fp=0xc000058c00 sp=0xc000058b78 pc=0x410727 github.com/lavalamp-/ipv666/internal/fanout.generate64NetworkHosts(0xc000076c60, 0xc000058f28, 0xc0069d40f0, 0x0, 0x10) /root/go/src/github.com/lavalamp-/ipv666/internal/fanout/fanout.go:263 +0x1a7 fp=0xc000058ef0 sp=0xc000058c00 pc=0x916667 github.com/lavalamp-/ipv666/internal/fanout.fanOut.func1(0xc00011e701, 0xc000076c60, 0x0, 0xc00011e700,...

All error printing is erroneously using %e right now. Change to %s.

The PersistentPreRun does not get invoked in the root command.

Add syncing functionality for aliased network ranges.

Make sure that ipv6.exposed can be accessed over IPv6.

Links to talks, statistics on data collected, etc etc. Perhaps this is `v0.5`?

When syncing addresses to S3 we should zip the files up first.

Current way of storing IPs in back-end is inefficient. Change to use bigints.