Re: [ANN ICO] HEAT: 3.0 crypto*multisig fiat*a2a hft*1000tps*DSA*PoS+PoP*e2ee chat*
@thezman007:
Thanks for your feedback.
Your interpretation of "private" as in private assets is understandable.
But it isn't the kind of private we talk about.
Private assets means its an asset that cannot be sold to anyone or traded among anyone, that isn't allowed to do so by the asset issuer.
A private asset issuer himself determines who is allowed to trade in those assets and the protocol simply denies anyone who is not on the "allowed" list to receive that asset or even place a buy order.
See this link for when I first introduced the concept (includes some more business oriented views on the matter from our project lead)
https://nxtforum.org/asset-exchange/private-assets-for-use-in-financial-institutions/
Thats an excellent use case, havent even thought of it being used that way.
But yes indeed, the power in the smart vouchers is of the course the smart part.
Which enables the issuer to remotely disable the voucher validity.
The challenge happens with little room for the challenger account, it can only act according to the rules defined by the protocol (for anyone interested please see the details about this in our whitepaper - James (jl777/supernet) actually helped me with that part
).
We are unclear right now whether the actual challenge generation code will run as a Distributed Services script or if we include it in the java code. Or a combination of those even.
In both cases, like with everything HEAT makes, it will be made available on our github repositories.
Thanks! and will do!
Thanks for your feedback.
You talk about private asset transactions. Will those tx's be viewable/searchable by anyone?
Your interpretation of "private" as in private assets is understandable.
But it isn't the kind of private we talk about.
Private assets means its an asset that cannot be sold to anyone or traded among anyone, that isn't allowed to do so by the asset issuer.
A private asset issuer himself determines who is allowed to trade in those assets and the protocol simply denies anyone who is not on the "allowed" list to receive that asset or even place a buy order.
See this link for when I first introduced the concept (includes some more business oriented views on the matter from our project lead)
https://nxtforum.org/asset-exchange/private-assets-for-use-in-financial-institutions/
What about using your Smart Vouchers to help solve Gift Card hacking problems. If you are not aware of them. Starbucks and other cards come on the market all the time on sites like bitify.com for 10-20% of their value in BTC. These were hacked or bought with stolen credit cards. Maybe HEAT can help corporations use your Smart Vouchers to make sure the right person is cashing in the card 
Thats an excellent use case, havent even thought of it being used that way.
But yes indeed, the power in the smart vouchers is of the course the smart part.
Which enables the issuer to remotely disable the voucher validity.
Will your challenger account be open source?
The challenge happens with little room for the challenger account, it can only act according to the rules defined by the protocol (for anyone interested please see the details about this in our whitepaper - James (jl777/supernet) actually helped me with that part
).We are unclear right now whether the actual challenge generation code will run as a Distributed Services script or if we include it in the java code. Or a combination of those even.
In both cases, like with everything HEAT makes, it will be made available on our github repositories.
Thanks guys, saw the interview, though in dribs and drabs at work and what I saw was good. Keep up the good work.
Thanks! and will do!