TF V4 Questions

#1

TF V4 Questions

We collect questions by community members pertaining to TF V4.

We will do our best to answer those questions during the next community call. Note that some info might be shared in time as V4 progresses.

Feel free to ask questions below or in the TFchats. We will update the main post.

References

It’s a good idea to start with TF V4 Docs: https://docs.threefold.io

Questions

  • what about the DIY nodes we have? …we will be able to transit to v4. but what about hardware requirements for existing and new DIY nodes?? | Reference: https://t.me/threefoldfarmers/79360
  • will there be different compensation e.g. DDR3 NODS VS. DDR4 Nodes | Reference: TF V4 Questions
  • Zos4 nodes doesn’t support set public config.
    In zos4 we pass the domain as kernel param at booting stage. What does this mean?
1 Like
#2

will there be different compensation e.g. DDR3 NODS VS. DDR4 Nodes

1 Like
#3

What kind of DIY hardware would be most useful to support the V4 grid? What can you say about some expectations, requirements that potential users/large customers have stated they’d want in their nodes? Think of generation, performance, bandwidth, gpu (basic or high-quality).

Is there anything you have in mind, except for supply/demand and usage-based rewards, to incentivise farmers to bring hardware to the grid that aligns with the answer to the first question?

In the documents it says INCA will have proof of capacity (for strategic locations) and proof of utilization. Can we assume V4 will have a base pay of some kind for all nodes, or is this base/proof of capacity reward just for nodes in strategic locations? Which locations are strategic, how is this determined?

I read that TFT will soon have the option to bridge to Solana. Is this INCA? Or will there be TFT on Solana next to this?

How and when do we get the option to swap TFT for INCA? Will this be before or after the public launch of INCA?

Is there an estimation for when V4/ Inca is going to launch?

How are farming pools created initially? Do these also mean we can team up our nodes with other farmers and share utilization rewards collectively?

Could you explain in detail what is meant by the 18-month vesting? Will all (farmed/granted) INCA be subject to this? Also the TFT-swapped INCA? If farmers choose to get paid in BTC, how does it work then?

It says Threefold V4 is self-healing. Does this mean there is going to be some kind of built-in redundancy? Maybe some interface where a user can set this up in an easy way?

That’s it for now. :slight_smile:
Regards, Marsh

1 Like
#4

Amazing. You’re on fire. Thanks.

#5

Can our farms with multiple nodes work as one node? This way instead of turning 5 nodes on with each 10% usage, we can turn one node on with 50% usage. When the usage increases the next node in line will automatically turn on. this will help save a lot on electricity.
If we are paid per usage in the future why should one have 5 servers on with each only a few percent utilized.

1 Like
#6

From imp221 on TG:

  • When will threefold do a proper marketing campaign?
  • And are we going to have some concrete dates with regard to V4 roadmap.
#7

3Phone - is about Volla OS, will we be there as an app or will we get a unique Android on it

1 Like
#8

It seems meanwhile there’s a lot more questions. I propose we take all the above, make a list and do a community call to get all those answered (and documented) one by one. Questions I have:

  • We heard that we expect one or 2 more months of TFT minting to reach 1B. After this the treasury will continue to pick this up. How much is on the treasury and how long do we estimate this will hold?

  • TFT will remain to exist and can be used 1 on 1 with INCA. Or converted. Or whatever. How is this going to work?

Now the word is out that ‘eventually’ all V3 nodes have to go to V4. If this is really the case;

  • We have 200+ customers, most of them not technical. So, how do we have them turn their nodes from V3 to V4 without bothering them with stuff they don’t understand or with making extra costs by sending things up and down?

  • Since V4 has it’s own Farm ID and Node ID, it sounds unlikely V3 and V4 can be mixed. How do we keep deployments on V3 while converting those nodes to V4?

  • Since all of the above has never been made clear, 90% of the V3 farmers wil have no clue that TFT is ending. So, we can certainly not throw this on them 2 weeks after they pruchased a V3 node (which is still the majority since V4 cannot be used for deployments). We need to inform them MONTHS ahead of what action is going to (or needs to) be taken on 6 months or more, preventing huge claims. (and as a vendor, I’m not picking them up)

We better prepare this very long ahead! (I’ll call Dany if you mess up)

1 Like
#9

Hi Robert,

I can’t answer all of your questions now, but I can start.

Here it might be helpful to know a bit about how we handled the v2 -> v3 transition. Farmers simply had to create a new v3 farm and Zos was able to update itself automatically on the next reboot. That is to say that there can definitely be a way for all farmers to smoothly transition.

The most likely outcome is that nodes that migrate to v4 simply cease to exist on v3 and thus any v3 deployments go offline. There might be some ways we can help ease migration of workloads from v3 to v4, but any kind of fully automated transition whereby v3 workloads survive the transition of a node to v4 is probably impossible.

Yes, I understand that any abrupt transition is not ideal. We are working on a plan and will take this into regard.

#10

Hi Scott,

Farmers simply had to create a new v3 farm and Zos was able to update itself automatically on the next reboot.

Then how come we need to make dedicated bootstraps now? Adding a V4 farm to their Threefold Connect App isn’t going to change the boot up is it? Most folks won’t know what a USB stick is, it was created by vendors. Would this still work?

The most likely outcome is that nodes that migrate to v4 simply cease to exist on v3 and thus any v3 deployments go offline. There might be some ways we can help ease migration of workloads from v3 to v4, but any kind of fully automated transition whereby v3 workloads survive the transition of a node to v4 is probably impossible.

Well, then this is where V4 stops. End of the road. For years you guys have been advertising the grid needed to be used. Now that we gave up our jobs and are in much need of business, we helped dozens of customers with making deployments for them. Soon that will include clusters etc. It is impossible…I say impossible…to bring those instances down because of an upgrade, unless you and Mik are coming over here for a couple of weeks migrating stuff. So…get this off the table, that is NOT going to work.

1 Like