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
{{ message }}
This repository has been archived by the owner on Dec 3, 2018. It is now read-only.
It is okay for the renter ant to require that there be hosts on the network. The renter ant should:
startup, get money. probably should run a miner all the time.
set a reasonably high allowance
set a contract window of 600 seconds (100 blocks)
Set a new allowance every 1000 seconds (purposefully slow + offset)
Upload a 500MB file every 120 seconds (20 blocks)
After 1260 seconds (10 files), it should delete one file at random every 120 seconds.
I would like a similar job called heavy renter, that does the same but with slightly different constants:
startup, get money. probably should run a miner all the time.
set a reasonably high allowance
set a contract window of 1200 seconds (200 blocks)
Set a new allowance every 1500 seconds (purposefully slow + offset)
Upload a 20 GB file every 480 seconds (80 blocks)
After 1200 seconds (2 files), it should delete one file at random every 480 seconds.
The host should probably also run a miner all the time. I don't expect 'heavy renter' to be successful on our current codebase. Though it seems like these values could be configurable, I think it'll be easier to think of them as separate jobs. We'll likely add more disjoint behaviors to each in the future, the fact that only constants have changed right now should be more viewed as coincidence rather than something that can be abstracted.
The text was updated successfully, but these errors were encountered:
It is okay for the renter ant to require that there be hosts on the network. The renter ant should:
I would like a similar job called heavy renter, that does the same but with slightly different constants:
The host should probably also run a miner all the time. I don't expect 'heavy renter' to be successful on our current codebase. Though it seems like these values could be configurable, I think it'll be easier to think of them as separate jobs. We'll likely add more disjoint behaviors to each in the future, the fact that only constants have changed right now should be more viewed as coincidence rather than something that can be abstracted.
The text was updated successfully, but these errors were encountered: