Data Egress Charges

Egress Charges (which I think were referred to as Network Units [NU] within TF previously?) are not included in the new python based TFT Farming Simulator.

I know it varies enormously depending on the type of workload, but egress charges can sometimes be the largest component of a cloud services bill so I think it’s important for farmers to understand how we charge for this and somehow factor it into our cultivation revenue models.

Does anyone have any data from AWS, Azure etc. to help us estimate this?

1 Like

Colin, thank you for the questions. In the original token simulator we had an estimated number of network units generated by the amount of CU and SU generated by the machine. In the screenshot you can see these highlighted in the top red box. The bottom red box has the unit price (set by farmers but TF Network will have a default price). In fiat the income generated by this (assumed) network traffic is between $36.40 for the smallest box and $1385.34 for the large one per month. This revenue was accounted for in the overall ROI calculation. It represents between 5.9% and 6.7% of the total overall income making up the ROI. We can take similar assumptions and add to the revenue stream in the new farming simulator.

The assumptions are based on best practise, if you have x amount of CPU and y amount of storage then an average amount of “network” is needed to work this capacity. I am happy to help and try to get to a better and more understood set of assumptions but the actual billing of this is going to work based on actual traffic in / out of TF Grid nodes.

The principle embedded in the billing mechanism accounts for traffic in and out (Received and Transmitted) for each node on which a consumer has CU and SU reserved. The only way to use zero-OS primitives (container, volume, 0-DB namespace, private network, kubernetes VM) is to connect to them over the network (the peer2peer encrypted wireguard network). Hence all reservations done will create network traffic.

Any architecture created, single node or multi node, will result in network usage and this will all be accounting towards the user (3bot wallet of) that makes this reservation.


Great answer Weynand, thank you.
I suspect these questions will soon be answered anyway, but I am assuming that consumers pay a fixed price for CU and SU in advance, but NU will have to be billed in arrears, creating a potential credit issue. Will there be a mechanism that ensures that the consumer can pay NU usage bills? Also, what will teh billing cycle be for NU - daily, weekly, monthly?