Pages:
Author

Topic: [JBS] Jumbucks - No IPO/ICO - Proof of Stake - Slack - DCR Stake Pool - 2+ Years - page 2. (Read 48226 times)

newbie
Activity: 53
Merit: 0
I just bought some jumbucks from bittrex.  I withdrew them to my coinomi app but despite multiple confirmations, the coins do not appear in coinomi.  I contacted coinomi support and they say the jumbucks community supported back end server is down and they can do nothing.  How do I get my coins back?
sr. member
Activity: 328
Merit: 525
Round 12 DCR stake pool pay out complete

14.82259281 DCR sold for 0.02519914 BTC
210.77928822 JBS bought for 0.02518601 BTC

.. except i kinda messed up and sent out 556.6492266 JBS total instead of 210.77928822 JBS. this will be reflected in later payouts.


The pool is slowly growing and represents 4.401% of all live Decred staking tickets.

So far the pool has paid out over 5546.94667026 DCR in total stake subsidy.

The pool was officially announced and opened on July 18, 2016, 11:18:29 AM.

Sign up today at: http://dcrstakepool.getjumbucks.com

If you require assistance, we are always happy to help in Jumbucks Slack.

Sign up to Jumbucks Slack to be a part of a growing community of over 640 crypto enthusiasts and Jumbucks fans!

Round 13 complete

18.08455276 DCR sold for 0.03255219 BTC
333.96490665 JBS bought for 0.03255209 BTC

This was more an adjustment round since I overpaid the last round. JBS payouts will resume next round.


The pool is slowly growing and represents 4.332% of all live Decred staking tickets.

So far the pool has paid out over 6486.45505826 DCR in total stake subsidy.

The pool was officially announced and opened on July 18, 2016, 11:18:29 AM.

Sign up today at: http://dcrstakepool.getjumbucks.com

If you require assistance, we are always happy to help in Jumbucks Slack.

Sign up to Jumbucks Slack to be a part of a growing community of over 650 crypto enthusiasts and Jumbucks fans!
full member
Activity: 143
Merit: 100
Why would anyone use this instead of ETC?
This coin differs from ETC by having a fair distribution of coins.

Well, not actually true: https://chainz.cryptoid.info/jbs/#!rich
As you can see in block explorer Top 100 addresses have 98.27% of coins.
How can we say that this coin is fairly distributed if only 100 people of 7,000,000,000 control almost 100% ? Grin

You can be in the top 20 by just filling your wallet with jumbucks on the cheap.
You only need 2,000 coins to be in your top 100, haha
Lets be fair when analyzing numbers.
hero member
Activity: 661
Merit: 500
We only want the FACTS!
Let me know if you need a Canadian translation Dev.   Tongue

Too funnie, eh!
sr. member
Activity: 630
Merit: 309
Why would anyone use this instead of ETC?
This coin differs from ETC by having a fair distribution of coins.

Well, not actually true: https://chainz.cryptoid.info/jbs/#!rich
As you can see in block explorer Top 100 addresses have 98.27% of coins.
How can we say that this coin is fairly distributed if only 100 people of 7,000,000,000 control almost 100% ? Grin
hero member
Activity: 2128
Merit: 520
Why would anyone use this instead of ETC?

This coin differs from ETC by having a fair distribution of coins. There is no developer premine, no funds obtained from exploits and no issues with replay attacks.
Also the improvements to the consensus systems will help with securing the chain and providing confirmations to exchanges. I wouldn't be surprised to see these improvements merged to other ethereum code bases

What is this coin for? How anyone can use it?

The coin is a currency for a lasting community from early in the altcoin days, jumbucks gets used quite regularly for tipping and friendly bets in the slack. Their have been several beta apps for the old code base that proved to be limited by the bitcoin code base to warrant further development. So in addition to the contracts developed in solidity being used, there will be several existing apps rewritten and services in place to provide value and use cases.
so nice to understand your explanation theres more room for achieving this purposes and let the coin state its value i guess it will make it success.
sr. member
Activity: 331
Merit: 252
Let me know if you need a Canadian translation Dev.   Tongue
newbie
Activity: 26
Merit: 0
Why would anyone use this instead of ETC?

This coin differs from ETC by having a fair distribution of coins. There is no developer premine, no funds obtained from exploits and no issues with replay attacks.
Also the improvements to the consensus systems will help with securing the chain and providing confirmations to exchanges. I wouldn't be surprised to see these improvements merged to other ethereum code bases

What is this coin for? How anyone can use it?

The coin is a currency for a lasting community from early in the altcoin days, jumbucks gets used quite regularly for tipping and friendly bets in the slack. Their have been several beta apps for the old code base that proved to be limited by the bitcoin code base to warrant further development. So in addition to the contracts developed in solidity being used, there will be several existing apps rewritten and services in place to provide value and use cases.
sr. member
Activity: 630
Merit: 309
What is this coin for? How anyone can use it?
hero member
Activity: 604
Merit: 500
Interesting project.

 Correct me where Im wrong...
You are changing algo to the forked eth algo
Name change
Equal swap out
Pow only until eth writes the casper code for pos
Basically like exp? Kr? Shift? Soil?

Thanks


Hi, here is a previous response I wrote to that question here on September 12 https://bitcointalksearch.org/topic/m.16230472

For the near term (at least 1 year) we intend on being Proof of Work.

Re-written now that the new name Ubiq is public:


This question has come up a few times.

Will Ubiq switch to 100% Proof of Stake when Ethereum's Proof of Stake Casper is released?

A switch to PoS isn't definite but we will evaluate and monitor Ethereum's Proof of Stake when it is released and had time to iron out any issues that may arise. A switch to PoS depends on the overall health of the Ubiq network and other factors such as ongoing distribution. It can make sense to just stay on PoW or a hybrid PoW/PoS network.

Another thing to factor in is that when Ethereum switches to PoS there will be excess mining capacity, so that can be another pro for sticking with PoW or a PoW/PoS hybrid.




Had the same question, thanks for the answer Smiley
newbie
Activity: 13
Merit: 0
Why would anyone use this instead of ETC?
sr. member
Activity: 328
Merit: 525
Interesting project.

 Correct me where Im wrong...
You are changing algo to the forked eth algo
Name change
Equal swap out
Pow only until eth writes the casper code for pos
Basically like exp? Kr? Shift? Soil?

Thanks


Hi, here is a previous response I wrote to that question here on September 12 https://bitcointalksearch.org/topic/m.16230472

For the near term (at least 1 year) we intend on being Proof of Work.

Re-written now that the new name Ubiq is public:


This question has come up a few times.

Will Ubiq switch to 100% Proof of Stake when Ethereum's Proof of Stake Casper is released?

A switch to PoS isn't definite but we will evaluate and monitor Ethereum's Proof of Stake when it is released and had time to iron out any issues that may arise. A switch to PoS depends on the overall health of the Ubiq network and other factors such as ongoing distribution. It can make sense to just stay on PoW or a hybrid PoW/PoS network.

Another thing to factor in is that when Ethereum switches to PoS there will be excess mining capacity, so that can be another pro for sticking with PoW or a PoW/PoS hybrid.

full member
Activity: 143
Merit: 100
Interesting project.

 Correct me where Im wrong...
You are changing algo to the forked eth algo
Name change
Equal swap out
Pow only until eth writes the casper code for pos
Basically like exp? Kr? Shift? Soil?

Thanks
sr. member
Activity: 328
Merit: 525
Round 12 DCR stake pool pay out complete

14.82259281 DCR sold for 0.02519914 BTC
210.77928822 JBS bought for 0.02518601 BTC

.. except i kinda messed up and sent out 556.6492266 JBS total instead of 210.77928822 JBS. this will be reflected in later payouts.


The pool is slowly growing and represents 4.332% of all live Decred staking tickets.

So far the pool has paid out over 5546.94667026 DCR in total stake subsidy.

The pool was officially announced and opened on July 18, 2016, 11:18:29 AM.

Sign up today at: http://dcrstakepool.getjumbucks.com

If you require assistance, we are always happy to help in Jumbucks Slack.

Sign up to Jumbucks Slack to be a part of a growing community of over 640 crypto enthusiasts and Jumbucks fans!
hero member
Activity: 604
Merit: 500
finally we can also see some price movements Smiley
full member
Activity: 121
Merit: 100
Very nice work. I am anticipating this launch.


Will solidity be compatible with this chain for development?

Yes solidity is compatible for development of contracts/dapps.
full member
Activity: 481
Merit: 102
Very nice work. I am anticipating this launch.


Will solidity be compatible with this chain for development?
legendary
Activity: 1078
Merit: 1050
Exponentially Subjective Scoring & Entering the final phases for Launch

So here's something I alluded to in a previous post. I wanted to take a look at eliminating the possibility of a long range re-org attack on the chain as this has been observed in other Ethereum forks.  Ultimately the best security for proof of work is having "sufficient" hash rate such that such an attack reaches the point of "not being feasible." The first idea I had for this was setting a limit on re-org depth, say 1 day. This solution on the surface seemed simple.. a little too simple so I sent Vitalik an email to see if he had any thoughts.

Here is Vitalik's reply:

Quote
The problem with limiting reorg depth to 1 day is that there's an attack vector where someone does a 51% attack that some nodes will see as being 1 day - 1 second and some nodes will see as being 1 day + 1 second, leading to a permanent split. One approach that could work is what I call "exponentially subjective scoring", which is defined as follows:

* Suppose that you are on a chain with score S1 (score = total difficulty). Suppose that there appears a new longer chain.
* Compute the "common ancestor" of the two chains; say that this ancestor has a score of S_a.
* Switch to the new chain only if (S2 - S_a) / (S1 - S_a) > 1.0001 ** (number of seconds between when S1 was received and when S2 was received)

The intention here is that you have a scoring mechanism which prevents long reorgs, as a reorg from one day ago would be penalized by a factor of 5650, but at the same time is friendly to timing discrepancies between nodes as if two nodes saw some block even one minute away then the chains would need to be almost exactly the same length for nodes to disagree as to the correct head of the chain.

I'd actually be quite excited to see this kind of mechanism tried out in a chain.

Exponentially Subjective Scoring is also further mentioned in this article that Vitalik wrote November 2014 - https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/

I'm pleased to say that I have coded this up and it works great. Here are some log lines which demonstrate this. ESS is basically another check which decides whether or not a re-org should take place.

Code:
I0924 00:59:07.674562 core/blockchain.go:797] == BlockChain exponentialSubjectiveScoring ==
I0924 00:59:07.674702 core/blockchain.go:800] ESS currentTime: 1474714747
I0924 00:59:07.674829 core/blockchain.go:814] ESS ptd (S_a): 1723872944000
I0924 00:59:07.675027 core/blockchain.go:822] oldBlock (S1) number: 14255
I0924 00:59:07.675169 core/blockchain.go:823] oldBlock (S1) difficulty:16380851
I0924 00:59:07.675350 core/blockchain.go:824] oldBlock (S1) Td:1723889324851
I0924 00:59:07.675471 core/blockchain.go:825] oldBlock (S1) time:1474714358
I0924 00:59:07.675637 core/blockchain.go:827] newBlock (S2) number:14256
I0924 00:59:07.675797 core/blockchain.go:828] newBlock (S2) difficulty:16345471
I0924 00:59:07.675972 core/blockchain.go:829] newBlock (S2) Td:1723905670322
I0924 00:59:07.676108 core/blockchain.go:830] newBlock (S2) time:1474714417
c:  1.9978401610514618
d: 1.0396644897858596
ESS Reorg
I0924 00:59:07.676607 core/blockchain.go:902] WriteBlock calling reorg
I0924 00:59:07.676730 core/blockchain.go:1096] == BlockChain reorg ==

The above lines are additional debug lines which I which are from a live test I did on the Testnet.  It's slightly confusing so here is a re-written version in Go which outlines the function using the exact figures from above.

Code:
package main

import (
"fmt"
"math"
"math/big"
)

func main() {

now := big.NewInt(1474714747)
S_a := big.NewInt(1723872944000)
S1 := big.NewInt(1723889324851)
S2 := big.NewInt(1723905670322)
S1_time := big.NewInt(1474714358)

// (S2 - S_a) / (S1 - S_a)
a := new(big.Int)
b := new(big.Int)
a.Sub(S2, S_a)
b.Sub(S1, S_a)
c := float64(a.Uint64()) / float64(b.Uint64())
fmt.Println("c: ", c)

// 1.0001 ** (now - S1_time)
d := math.Pow(1.0001, float64(now.Uint64())-float64(S1_time.Uint64()))
fmt.Println("d:", d)

// Comparison
if c > d {
fmt.Println("Reorg")
} else {
fmt.Println("No reorg")
}
}

The output is as follows.

Code:
c:  1.9978401610514618
d: 1.0396644897858596
Reorg

This code change actually took a bit longer as it required a lot of testing and learning how Ethereum handles new blocks being processed and the different scenarios. i.e. had to run through a lot of the following cases:

1 new block comes in
2 new blocks come in
3+ new blocks come in
1 new mined block pushed out the network
2 new mined blocks pushed out to the network
3+ new mined blocks pushed out the network

So most of the work was actually figuring out how block processing works and testing the scenarios and thinking more about "when should this be checked?" and further thinking of other cases where it could go wrong.


So just to re-cap JBSEE will come out with 2 new consensus level changes.  These are:

Exponentially Subjective Scoring - A deterministic scoring system when comparing two chains. The longer the reorg, the higher penalization, and the less likely the new chain will become the main chain. It is more expensive to attack a well publicized good chain.

Rewritten difficulty algorithm based on Digibyte's Digishield V3 - Difficulty algorithm that is battle tested on numerous coins and is far better suited to longer block times and fluctuations in hash rate.

It is also worth noting that no other Ethereum fork has the level of new code and consensus changes that the JBSEE network will have.


Here are the priority items in the next few weeks. It is a tight deadline but we are aiming for a launch of the network before October 11th next month.

Launch of new coin

All the technical details set and we are co-ordinating with exchanges.

PRE-ANN thread

The details are being written up. This will be up shortly.

Swap system

This has been outlined in a previous post and will again be outlined in the PRE-ANN. The sites for a non-exchange swap are being completed.

Code modifications

These are complete for the launch. We are also thinking of paying a Geth dev to code review the new code changes I have made just to have another pair of eyes go through the code.

Logo and branding

The new logo and name has been chosen.


Thank you. Bought more of this good coin Smiley
sr. member
Activity: 295
Merit: 250
Great news, looking forward for new PRE-ANN...
Pages:
Jump to: