mfw78

Actually, a much tighter solution to this would be to enable an EIP-712 signatures on `dilute` so that `owner` could sign a dilute. This would represent significant UX/DX experience, allowing...

Yes, I certainly agree the fixed length isn't optimal, and that's why for the next phase I was very much looking at the magic value approach, and generalising this for...

> I see no problem with leaving both available. But I do think that setting by "volume+duration" should be the default recommended method, and "depth+amount" should be relegated to an...

Hi, just kindly wondering if there is any resolution to this? I'm coming up against the same issue and am curious as to how #1275 fixes this, and if there...

IMHO then, it seems that this issue should be re-opened? :pray:

Just confirming, is there any ability within this using the new slack app to post in a channel within slack using a nickname that isn't the same name as the...

A completely different approach to this (as opposed to building this within `bee` somehow), would be having workloads run on cloud providers that are able to spin up ephemeral nodes,...

> I would like to add a short feedback from the contracts usage/integration, particularly in the bee node implementation. > > Given that there are a few contracts that are...

An example of where this pattern has been used extensively: https://github.com/sky-ecosystem/dss-chain-log

Just pass along the version as well that `bee` is running with `Register.get('COMPONENT', '2.6.0')`. In which case, upgrading the node is an implicit agreement to the new contracts (if applicable)....