That’s an interesting question and something I’ve thought about. It’s difficult to give a number as it depends on how much of stack you’re hosting and how much more data will need to be served as HiFi develops/features are added.
At this time serving of metavoxel data and assets (entities) consume bulk of traffic so you see bursts as people come in, then, for my setup, see it slow to around 0.07mb/s per av, a bit more if voice is in play.
With the distributed nature of the assignments system it will be possible to host high bandwidth items on external services leaving the lower volume portions on your local machine, greatly lowering peak bandwidth needs. You might only run domain locally farming all the assignments to externals, or select services.
You would pay a cibt/interval charge for external services, only paying when you’re using if going that route. How much that would be depends upon the value of cbit to real money and what the market will bear. I intend to offer assignment services from East and West Coast USA, and I have no doubt others will as well, around the globe. I’ve already crunched some numbers and I’m seeing figures in the pennies per hour range as target points.
That being said - rolling it all on your own, here’s what I’ve seen here and now.
35mb/s down, 5mb/s up cable at home. Have had 5 avs in domain and didn’t notice any issue or excess lag for them to load domain. That was using the local machine to serve all content.
I think better answers to this will come in a few more months as things firm up more.