Search content
Sort by
Showing 14 of 14 results by johngoodmanbtc
I was wondering how I can go about acquiring some BEER tokens. I figure it would be a fun thing to throw one or two at a friend as a joke or something.
Here is the token address:
https://ethplorer.io/address/0xd63656d216b709466730e59cea4d5da88dbf3c2a
Here is the token address:
https://ethplorer.io/address/0xd63656d216b709466730e59cea4d5da88dbf3c2a
This whole project could revolutionize the entire insurance industry!
Just last year I purchased a pre-owned vehicle. Due to negligence from the previous owner, oil consumption was a major issue. I brought this issue to the attention of the dealership on multiple occasions, but they chose to ignore the problem.
Then it happened. The car broke down in the middle of a highway. Fortunately, my insurance company covered the cost of the tow to the dealership. They tore down the motor to discover the root cause. It was over 12 hours of work just to tell me they had condemned the motor. The cost of the repair was another $3,000.
The worst part about the entire experience? My insurance waited until all the work was done to tell me that it wouldn't be covered. I was infuriated!!
I really do have faith in this project. Fewer people should experience what I had to go through.
Just last year I purchased a pre-owned vehicle. Due to negligence from the previous owner, oil consumption was a major issue. I brought this issue to the attention of the dealership on multiple occasions, but they chose to ignore the problem.
Then it happened. The car broke down in the middle of a highway. Fortunately, my insurance company covered the cost of the tow to the dealership. They tore down the motor to discover the root cause. It was over 12 hours of work just to tell me they had condemned the motor. The cost of the repair was another $3,000.
The worst part about the entire experience? My insurance waited until all the work was done to tell me that it wouldn't be covered. I was infuriated!!
I really do have faith in this project. Fewer people should experience what I had to go through.
I do not know much about this umbrella coin, the first step if you want to invest, learn everything first, and whether this coin will be quite bright future? Let's wait and see.
The idea seems pretty original. The team appears to be pretty reputable. They've got my support so far. Less than a week from the ICO!!
Looks like their dev team is hard at work. I found out through Facebook that they've got a pre-alpha in the works.
https://medium.com/@umbrellacoin/dev-update-week-of-july-30th-c5a073206df4
https://medium.com/@umbrellacoin/dev-update-week-of-july-30th-c5a073206df4
What makes Umbrella Coin a unique type of cryptocurrency?
From what I can tell, it looks like they're trying to create a system that allows you to "buy" a policy with UMC, and then get up to 3x your money back with a validated claim from the community. Seems like a good idea
This seems like a very exciting project! A few questions I have.
1. How long will the ICO be open for?
2. Are there any incentives beyond the first 2 days?
3. Why did you choose the Ethereum platform over others like NEO?
At this rate, the community will be built in no time!
1. How long will the ICO be open for?
2. Are there any incentives beyond the first 2 days?
3. Why did you choose the Ethereum platform over others like NEO?
Hey everyone!
I just wanted to give a quick update on what the dev team has been working on. Our team has grown quite a lot over the last week, and people have been ramping up on the existing code base and our proposed architecture. Some of the devs have been on vacation, so weâre hoping to have a âhackathonâ this upcoming weekend to really make some headway into a prototype and at least have some basic workflows working.
On Friday, we met and discussed some of the outstanding questions regarding the community, fairness in voting, and the optimal way to launch. We ended up taking a lot of notes on a napkin :-) http://i.imgur.com/RiIbX0w.jpg
We agree that limiting the maximum/minimum payouts initially is a good idea until we reach equilibrium in the float pool. We also had very interesting discussions about how votes should be weighed, how to incentivize people to vote on claims, and minimum votes required to pay out. We are leaning against weighing votesâââthat could devolve into an oligarchy type situation. Those with the biggest policies, the most reputation, or otherwise the greatest vote weights could be in a position of tremendous power. We want to avoid introducing this unfairness and really let the community evolve organically. We are also leaning towards policyholders paying a small fee in UMC with that paid out to users voting on their claim. This fee will be used to pay people to vote on the claim. We like this idea for two reasons. A) It incentivizes people to vote on claims which have fewer votesâââthis means they get a bigger piece of the fee than a vote that has many votes. Avoiding a flat payout encourages participation distributed across claims. B) It will discourage people from submitting fraudulent claimsâââthey would have to pay the fee and, if their fraud was discovered, they would lose their policy entirely. In the same vein of community growth and reaching a consensus, we want the community to have a forum for discussion for each claim. We want theme to share information and allow their expertise in certain areas to show. We also want to prevent users from submitting duplicate claims, or submitting duplicate evidence across accounts. Weâre thinking of having a âsimilarity scoreâ between two claims based on the parameters submitted when making a claim (amount, area, day of occurrence etc.) and the data they submit (receipt, video, photo) and giving that information to users.
The team is really excited to build this product and get something working and able to be used by the community quickly. We want to surface as much information as possible to let the community reach a consensus in a fair and reasonable manner, and build on this system going forward.
Thanks for your continued support!
this team keeps on moving. love it!I just wanted to give a quick update on what the dev team has been working on. Our team has grown quite a lot over the last week, and people have been ramping up on the existing code base and our proposed architecture. Some of the devs have been on vacation, so weâre hoping to have a âhackathonâ this upcoming weekend to really make some headway into a prototype and at least have some basic workflows working.
On Friday, we met and discussed some of the outstanding questions regarding the community, fairness in voting, and the optimal way to launch. We ended up taking a lot of notes on a napkin :-) http://i.imgur.com/RiIbX0w.jpg
We agree that limiting the maximum/minimum payouts initially is a good idea until we reach equilibrium in the float pool. We also had very interesting discussions about how votes should be weighed, how to incentivize people to vote on claims, and minimum votes required to pay out. We are leaning against weighing votesâââthat could devolve into an oligarchy type situation. Those with the biggest policies, the most reputation, or otherwise the greatest vote weights could be in a position of tremendous power. We want to avoid introducing this unfairness and really let the community evolve organically. We are also leaning towards policyholders paying a small fee in UMC with that paid out to users voting on their claim. This fee will be used to pay people to vote on the claim. We like this idea for two reasons. A) It incentivizes people to vote on claims which have fewer votesâââthis means they get a bigger piece of the fee than a vote that has many votes. Avoiding a flat payout encourages participation distributed across claims. B) It will discourage people from submitting fraudulent claimsâââthey would have to pay the fee and, if their fraud was discovered, they would lose their policy entirely. In the same vein of community growth and reaching a consensus, we want the community to have a forum for discussion for each claim. We want theme to share information and allow their expertise in certain areas to show. We also want to prevent users from submitting duplicate claims, or submitting duplicate evidence across accounts. Weâre thinking of having a âsimilarity scoreâ between two claims based on the parameters submitted when making a claim (amount, area, day of occurrence etc.) and the data they submit (receipt, video, photo) and giving that information to users.
The team is really excited to build this product and get something working and able to be used by the community quickly. We want to surface as much information as possible to let the community reach a consensus in a fair and reasonable manner, and build on this system going forward.
Thanks for your continued support!
At this rate, the community will be built in no time!