I cant talk with your customers but my initial thoughts are that you should focus with laser-like attention to your customer needs. There are a lot of "ands" in your product. Who is your ideal customer? Is it whales tracking multiple cryptocurrencies?
Is your ideal customer dev teams keeping their coin alive with DCA arbitrage across multiple exchanges?
The biggest argument is the other coin networks that have been running for years in production without proof of work.
Nano and EOS have interesting consensus models. Nano manages to remove all inflation and transaction fees and is just a base level currency. EOS has an account fee and you have to rent resources but can do code execution on transactions (smart contracts). They both rely on accounts voting for representatives and have had similar problems with spam.
Nano has been running for > 4 years and EOS for > 1 years.
Thank you for your writeup. I understand the idea behind the network partition and I've been doing some digging. It looks like there are numerous commits attempting to address this edge case (they call it frontier cementing).
Here is a writeup I found on reddit that further elaborates this:
"""
There is a (currently hypothetical) edge-case where this could be reversed (not exactly the same as PoW chain reorganization due to forking, but similar.) In this edge-case:
We imagine the Internet has, right now, been carefully split by a malicious attacker into two exact halves
The Internet halves would be carefully contructed to each hold >60m online Nano votes. (This Internet fracture has never actually happened in Nano's lifetime. There are not 2 x 60m votes currently online.)
The attacker double-spends on a coffee (or house) in two of your stores worldwide just now
They then allow the Internet to heal
One of their transactions will be reversed by majority voting.
So while Nano transactions are fully-confirmed, they are not currently immutable.
Since there are not >120m votes currently online, it has not happened and cannot currently happen either. No previous-to-today Nano transactions will ever be reversed.
""" -- throwawayLouisa https://www.reddit.com/r/nanocurrency/comments/bgdshq/what_i...
Can you elaborate on the network partition issue that you found with nano? As far as I know nano has been live for years without a doublespend or downtime and thats pretty impressive.
GAN improvements that lead towards finding global minima for any given distribution mapping. GANs are versatile but still suffer from mode collapse and instability, drastically reducing their utility.
Capitalism can be thought of as a complex learning system. We, as a society, want people to contribute the most that they can to the overall goals of humanity and capitalism acts as a vehicle for that.
Comparing it to another popular complex learning system, neural networks, might provide insight on failure conditions.
Income taxes can be thought of as gradient regularizers.
Basically limit the amount of weights accumulated per training session (wealth per tax year). Estate taxes can be thought of as weight regularizers (that occur once per lifetime). Maybe it would be more palatable as a tax on wealth yearly.
One of the ways that networks fail (and capitalism can fail) is with extreme values on weights (wealth) on small portions of the network. There are ways to counter this on a neural network - some are heavy handed (l1, l2 regularization), but some are just clever without direct analogies (dropout, batch normalization, etc).
I wonder how the conversation would change if we had to calculate our income tax as a percentage of total wealth each tax year.
This is an implementation of generative adversarial neural networks. The aim is to allow developers to use generative and discriminative networks in their applications.
This is exciting because the possible applications of generative content are vast and largely unexplored.
SEEKING WORK (Denver; Remote) Full Stack senior engineers
We are a dev shop with two senior developers that have been using Ruby since 2005. We attended the first Rails conf and have a decade of experience developing full stack solutions.
Code examples available upon request.
We <3 bootstrappers and startups. Email me at mikkel[at]255bits.com Keywords: Ruby, Devops, Docker, Node, React, CouchDB, SQL, Rails
SEEKING WORK (Denver; Remote) Full Stack senior engineers
We are a rails shop with two senior developers that have been using Ruby since 2005. We attended the first Rails conf and have a decade of experience developing full stack solutions.
Code examples available upon request. We <3 bootstrappers and startups. Email me at mikkel[at]255bits.com Keywords: Ruby, Groovy, Devops, Docker, Node, React, CouchDB, SQL, Rails
We also have web apps used by thousands daily, using a variety of languages and technologies.
https://www.255bits.com/
SEEKING WORK (Denver; Remote) Full Stack / Machine Learning senior engineers
We are building a platform to help businesses utilize machine learning solutions. We offer consulting for new solutions and optimization on existing solutions.
Code examples available upon request.
We <3 bootstrappers and startups.
Email me at mikkel[at]255bits.com
Keywords: JS, Ruby, Python, Groovy, Devops, Docker, Node, React, CouchDB, SQL, Rails, Tensorflow, Machine Learning
We also have web apps used by thousands daily, using a variety of languages and technologies.
SEEKING WORK (Denver; Remote)
2 Full Stack / Machine Learning Engineers
We are two polyglot full stack senior engineers.
We've both used Ruby since 2004 and Rails since version 0.13. We have a few web apps (used by thousands daily) that run on NodeJS / Cloudant / Docker / React.
Less than a year ago we both stopped consulting to study machine learning and build products full time.
Both of us have worked with startups and large data companies in the past and understand a lot of the challenges with getting data into the right place & format. Additionally, we've been working with machine learning for a year.