Answers in Bold. Just like the model proposal, these are the best answers we can provide at this stage. as we test the system in real-life or at increasing scale, some of these notions and parameters may evolve.

Q: (ManyNothings)

The most important question. What defines the timespan/size of a Bundle? How many Bundles do you guys estimate will be produced per day on the network?

the timespan of a bundle is defined by the business or regulatory requirements for availability of data about a product, i.e. after what time the data will stop being valuable and could be safely deleted (e.g. in normal conditions you would not necessarily want to store data about origins of raw ingredients in meat sold in the 1980s; unless there was an outbreak of disease or some other problems, such data would probably become uleless within 2-3 years max; with some other products, such as medicine, the length of storage may be longer due to regulations; for some things, like spare parts for airplanes for example the lifespan of data (and thus bundles) can exceed 30 years and thus long-term resilience would be required. Assuming the successful roll-out and adoption of AMB-NET, we would be talking about millions of bundles produced daily.

Q: How are Challenge fees going to be allocated between the 3 Atlas nodes? Section 4.2 mentions that the first Atlas node that responds wins the Challenge fees, but then what is the benefit to the user of a tiered system if speed is all that matters?

more senior Atlas nodes will get a higher allocation of Challenge fees (specific numbers/models will be releaseed in due time, but the point is that 1 Atlas Sigma node would on average receive more than 3 Atlas Zeta nodes combined, and similarly 2 Atlas Omega nodes would receive more than 5 Atlas Sigma nodes, and so on). Importantly, performance requirements for Omega will likewise be higher than for Sigma or Zeta, etc. Again, there will be a more detailed model featured which will outline the mechanisms. We want to find the right balance between the community and corporate interests in the network.

Q: The Storage Fee split (6.2) mentions that 45% will go to "participating masternodes." What is a "masternode" here? Is it every node on the network? Just particular kinds of nodes?

Nodes that are part of AMB-NET. At the early stages implementation of KYC for masternodes will be done in a centralised manner to assure the integrity of the network and prevent malicious actors from entering. Thus someone may run a masternode, but if they do not pass KYC, then they would not be a participatory node in AMB-NET.

Q: (Les_Top_Hat + similar question by fish2018): AMA question for /u/angelversetti - how many bundles can be stored by a Zeta node per year?

The model discussed above will ensure that the number of bundles allocated to each type of nodes is commesurate with the storage requirements for the said nodes.

Q: (stokarz): Question for Angel: if I don’t have enought AMB for Atlas node, will I be still able to stake coins by Perseus Node or other stake mechanism? When will this all be runing live? After main net released?

Perseus Nodes are not masternodes and do not have staking mechanisms. Yes, after the main-net launches as per our Roadmap , we plan to start onboarding node operators

Q: (mozzarn) Hermes and Apollo are not for regular AMB holders. They are companies storing data on the blockchain. Only Atlas will be available for us normies

Apollo nodes will also be available to the wider public. Hermes, being data producers, would largely make sense to companies, but are not necessarily going to be restricted to companies. We are working with Quality Assurance associations and standard-setting entities, they appear to be potential operators , or users, of Hermes nodes. We are also exploring models where Apollo/Hermes nodes are operated on behalf of another stakeholder, or providing services to third parties. These are some of the exciting solutions we are researching, and over time there may be new models emerging in terms of accessibility of nodes.

Q: (watchthemusic): What kind of uptime and processing power are we talking about to run a 10k masternode? Can people do it on a gaming pc that runs 24/7 or are we talking about renting a VPS?

technical requirements will be provided. For Atlas nodes the requirements are likely to be more relaxed, as their underperformance does not hinder the industrial utility of AMB-NET itself. For Apollo Nodes the requirements will be the strictest, and selection process - most rigorous. Additional details on technical requirements will be provided in due course, our dev team is now testing this.

Q (Wlcat): Hey Angel, I appreciate you taking the time to answer questions. That type of involvement is one reason I became involved with Ambrose.

I did have a couple of questions. Can you have 2 10k nodes? I'm assuming you can upgrade later? I'm at 15k now, can I enhance my node revenue if I stake those as well? Yes, you will be able to have 2 10k nodes. See my comments about the seniority of nodes and different challenge fee opportunities in answer to one of the questions above

I understand that from a regulatory stand point it is important that we perform tasks for our token distribution. I'm used to dealing with the SEC and CFTC, but my technical knowledge is limited. What would my responsibilities be as a node holder?

regulatory aspects are a fundamental influnecer of our architecture and network design. You can already see our initial discussions of risk management and commitment to KYC/AML regulations. More on that will be provided in due course.

Again, thank you for your time. I was completely confused with everything yesterday, but am now back to being excited,

welcome

Q (jaggedsoft): Are there any partnerships and programs you can disclose right now that are no longer under NDA?

everything that would no longer be under NDA, would be communicated. I will note for the public record that ALL the corporations with whom we signed NDAs are still working with us, with interactions being at different stages, from developing PoCs to pilot projects to actual implementation and even running an Ambrosus Masternode. None of our interactions with major corporates have broken down. We will make public announcements in due course, when this will make sense for our partners. We are aiming for a long-term relationship with them and adoption of AMB-NET, and not short-term hype to satisfy the speculators.

Q: (YashiLou):

Congratulations on the AMBERnomics. Just a few Q's from my end:

With regards to creating a bundle, how many individual items could there be on it in total? I.e. If a producer makes 1000 bottles of Coca Cola, is it possible to put ALL of them into one bundle or is there an upper limit of how many they can input?

The point there is not to have to put every single sensor reading on the blockchain (which would give you billions of transactions per day), which is why data is bundled and compressed proofs are uploaded. A bundle is likely to have a fixed number comprised of multiplication of the number of Assets and Events, i.e. either a lot of assets with few events, or a few assets with many events related to them. Again, as we are running pilots with corporate partners in food/pharma sector, it can allow us to see in practice how pricing of bundles would work. Given that it's an entirely new mode of data management, there are no precedents that can guide us on that, so we literally have to determine the outcome of bundle limits and pricing based on pilots.

Assuming one is able to stake for an Atlas node, how exactly will this be staked? For example; will this be through a special "wallet" being created that we'll use? And imagining that this is a possibility, is there a minimum time limit on how long one could have a MN, or is it just until the date being sheltered on it expires/the data is shifted over to a new MN?

There are currently legal uncertainties that prevent me from answering this question for you now. Mere usage of wallets is in general not very welcomed by regulators. We are working on solutions where running a node would provide specific utility to network (resilience and data availability are a couple of basic examples), but for lower-tier nodes this may translate into merely having your laptop connected to the internet, or having basic VPS running. More details will be provided by our devs soon.

Can you disclose any information about the hardware technical requirements that each MN would require so as to be run?

This will be provided in due course. As noted above, Atlas will have less stringent requirements, whereas Apollo will be very high

As for the penalties for offending users of the network, could you offer any figures, or a concrete example, for different offences that you may be referring to?

malicious activities on the network, which in general may include offering inconsistent versions of the truth, validating wrong inputs, having no data available when challenged or attempting to supply false data. The penalties would start with a very low figure (we start with an approx. 1% of stake), but will double for every repeated offence on the network. We will also look into the models where intentional and unintentional offences are punished differently, similar to how the law works in most societies.

These are all the questions I have spotted so far. Hope the answers make sense.

This is a great case study as to how blockchain can be integrated into a business. I like the different node types and functions, it shows that a lot of thought went into it.

From an adoption perspective it's great that the price is defined in usd, no reasonable company would agree to pay such volatile prices. However, since the usd cost is fixed it means that the network value also can be calculated. Probably makes this more of a long long-term thing, but I love the approach. Shows that they came to play!

Hi Angel, thanks for taking the time to answer some questions about the tokenomics. Here are mine:

The most important question. What defines the timespan/size of a Bundle? How many Bundles do you guys estimate will be produced per day on the network?

How are Challenge fees going to be allocated between the 3 Atlas nodes? Section 4.2 mentions that the first Atlas node that responds wins the Challenge fees, but then what is the benefit to the user of a tiered system if speed is all that matters?

The Storage Fee split (6.2) mentions that 45% will go to "participating masternodes." What is a "masternode" here? Is it every node on the network? Just particular kinds of nodes?

If I remember correctly, when the community was asked about its opinion on how the fee system should be based within the ecosystem, it was a resounding "FIAT!" due to the lesser volatility that it is subdued to vs current crypto volatility. Traditional businesses will resonate much better with fiat, for now, too until the sector matures and then it could be possibly changed to crypto further down the line.

AMA question for /u/angelversetti - how many bundles can be stored by a Zeta node per year? If Zeta nodes are rewarded $1 per bundle in the form of a challenge fee then this gives us some quantifiable maximum ROI. Thanks for answering!

Angel, I think it would be very helpful if you could provide more details in terms of the estimated frequency of the challenges per each node level and roughly how much these challenges will reward each corresponding node level.

AMB-NET prices AMB transactions in terms of Nectar, a specialized unit that measures the computational intensity of various actions on the network, and on a floating scale, akin to the concept of Gas in Ethereum. Thus, Nectar costs rise as data transactions become larger or more complex. In certain market environments, Nectar’s floating rate can also reinforce AMB-NET price stability, ensuring that Storage and Transaction Fees never become unreasonable or hinder the industrial adoption of AMB-NET. Thus, Nectar and Amber have a dynamic relationship to facilitate harmonic interaction between different stakeholders of AMB-NET.

If it's like Gas in Ethereum that would mean AMB is used for transactions instead of a 2nd token. Since ETH is a 1 token model.

And with VEN/THOR if the cost rises due to larger transaction or it's more complex, the users can use their own computer power in place of extra THOR to keep the price of the transaction lower which may be ideal for people and enterprises who will be doing large and complex transactions.

And with the 1 token model that means users will be spending their AMB every time. Which may or may not be good depending how you look at it. Since the more AMB you have and the higher the price goes, the richer you get. If you're forced to spend AMB every time you want to do something that may not be a benefit to some people.

The transaction cost is fixed though, so it does not matter whether AMB is 50¢ or $50. The associated fees collected will remain the same. The incentive to buy and stake (Perseus peer-node) them is in order to reach master node status or as use on the network for storing data.

So, essentially it will be burning of coins? I think what we need is an explanation for what AMB and Nectar will be doing specifically. If Nectar is used as transactional power, is the amount pre-determined and diminishes over time? Or will AMB-tokens be spent in order to convert them into Nectar?

No. Nectar is a value that exists inside of the network itself and measures the amount of computational power used to perform a particular transaction. This is important, because you can assign to Nectar a fixed value in USD, which then can be translated to AMB without a change in the net cost of the transaction due to AMB prices changes.

So challenge fees only occur if the entity utilizing Amber challenges something in the blockchain between the transaction points? Then that Atlas node becomes the repository of that information proportional to the holding period. What does that mean?

Thank you for that post. I have enough for a node, but I don't have a clue as to the requirements other than staking tokens. How often would a challenge even occur? Is it worth getting a higher node etc.

Hey Angel, I appreciate you taking the time to answer questions. That type of involvement is one reason I became involved with Ambrose.

I did have a couple of questions. Can you have 2 10k nodes? I'm assuming you can upgrade later? I'm at 15k now, can I enhance my node revenue if I stake those as well?

I understand that from a regulatory stand point it is important that we perform tasks for our token distribution. I'm used to dealing with the SEC and CFTC, but my technical knowledge is limited. What would my responsibilities be as a node holder?

Again, thank you for your time. I was completely confused with everything yesterday, but am now back to being excited,

With regards to creating a bundle, how many individual items could there be on it in total? I.e. If a producer makes 1000 bottles of Coca Cola, is it possible to put ALL of them into one bundle or is there an upper limit of how many they can input?

Assuming one is able to stake for an Atlas node, how exactly will this be staked? For example; will this be through a special "wallet" being created that we'll use? And imagining that this is a possibility, is there a minimum time limit on how long one could have a MN, or is it just until the date being sheltered on it expires/the data is shifted over to a new MN?

Can you disclose any information about the hardware technical requirements that each MN would require so as to be run?

As for the penalties for offending users of the network, could you offer any figures, or a concrete example, for different offences that you may be referring to?

2.7 Nectar

AMB-NET prices AMB transactions in terms of Nectar, a specialized unit that measures the computational intensity of various actions on the network, and on a floating scale, akin to the concept of Gas in Ethereum. Thus, Nectar costs rise as data transactions become larger or more complex. In certain market environments, Nectar’s floating rate can also reinforce AMB-NET price stability, ensuring that Storage and Transaction Fees never become unreasonable or hinder the industrial adoption of AMB-NET. Thus, Nectar and Amber have a dynamic relationship to facilitate harmonic interaction between different stakeholders of AMB-NET.

"Legal Disclaimer:This is intended to be a technical vision summary of a cryptoeconomic model to power AMB-NET platform. It provides as much detail as is possible at this stage of development of the platform.Rigorous testing of these models will be implemented in the forthcoming weeks ahead of the launch of the main-net and may result in some changes to the specifications and staking mechanisms.Amber (AMB) is a utility token within AMB-NET. AMB is not a financial instrument and should not be considered as such.Participation in AMB-NET provides a range of technical utilities to stakeholders and enterprises, and should not be considered as a speculative activity, financial transaction or an investment of any sort."

If it's like ETH then it's the 1 token model. You don't generate anything.

Which means if you hold 10,000 AMB to meet the requirement for a master node and transactions require AMB to pay the gas, then you do 1 transaction and you're below 10,000 AMB and you lost your master node?

And the more complex or bigger the transaction the more gas (AMB) it costs.

With VeChain THOR if the transaction is bigger and more complex then instead of paying more THOR (gas) you can use some of your own computer power in place of paying more THOR (gas) to help keep the price down.

If you're an enterprise doing large and complex transactions you will want to go with the cheapest option. If AMB says the bigger the transaction or more complex the more gas (AMB) you will need and VeChain says hey instead of paying more THOR just use some of your computer power instead to save money...which one would the enterprises who are looking to save money go with? And VeChain is making the THOR price stable.

The Ambrosus network is a blockchain-based ecosystem for supply
chains, ensuring the origin, quality, compliance and proper handling of items tracked by the network. Ambrosus’ primary focus is on improving supply chains for life-essential products, specifically food and medicine, although the protocol can be applied to almost any complex supply chain.