There is only one way to prove that and that is by breaking it today but that would be pointless and very expensive and DigiByte would not fall down unless you were able to continuously maintain the stress at which point we would have to admit that it wasn't as scalable as presently programmed, if it did fall over. But then we would change the code and move on. The scalability of DigiByte is layed out in a 20 year plan, we are expecting much to change in this time. So DigiByte is as scalable as described!

15 seconds is not set in stone as the DigiByte block time. It is made up from 5 algorithms each with averaged block time of 75s. So the averaged time for the whole of Digibyte is a block being found every 15s. You cannot debunk JCs basic math problem but you can say there are variables that come into play that are more than likely going to defeat it because it is a future problem for DigiByte that he is asking you to solve with today’s tools, where nothing on the network is capable of verifying the transactions fast enough. I don’t think this is actually true today and it will be even less so in the future. This is why he wants to stick us to an imaginary constant flow of 43 second transactions but think about what that actually means. It means we would be running at full capacity constantly where nothing had a chance to catch up, it’s just ridiculous really and we would be competing with VISA today.  

Why does individual algo block time matter here? It doesn't!
DGB block time is 15 secs, right?

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

That's some whale accum voodoo right there.  Hold out just long enough to shake out weak hands like mine..... smh.

Don't worry MEME is going in Positron Technologies LLC accelerator it will be huge 

Tell him to compile one. I'll give him 500.

Yap
I think 10 out of 16 mill mined now.

lol some fools sended all coins over there and start to dump.. xD

You might regret that bois.

ive reached out to several POS staking sites.. and the cool people at www.coinwallet.co are interested in adding TRI! but they are having few problems on compile.. if dev is here or ayone who is able to help ethought fix this so we can get this cool coin listed!



heres the email i got from coinwallet.co



"I just tried to build Triangles from source but again get this error:

HAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/net.d -o obj/net.o net.cpp
net.cpp:57:37: error: ‘USE_UPNP’ was not declared in this scope
 bool fUseUPnP = GetBoolArg("-upnp", USE_UPNP);
                                     ^
net.cpp: In function ‘void run_tor()’:
net.cpp:1947:5: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
     };
     ^
net.cpp:1947:5: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
net.cpp:1947:5: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
makefile.unix:273: recipe for target 'obj/net.o' failed
make: *** [obj/net.o] Error 1

Any ideas how to fix this?

Thanks

ethought"


TRI is still alive.. you know why... hold strong!

make -f makefile.unix "USE_UPNP=0"

make -f makefile.unix "USE_UPNP=-"

Enter the Cryptographic Triangles Matrix    http://pastebin.com/raw/JS7mycYL

Here's the emission curve untill the next halving.

Date / Created by Month / Total / % of the total.

01/2016 : 622 000 / 622 000 / 5.65%
02/2016 : 208 800 / 830 800 / 7.55%
03/2016 : 223 200 / 1 054 000 / 9.58%
04/2016 : 216 000 / 1 270 000 / 11.55%
05/2016 : 223 200 / 1 493 200 / 13.57%
06/2016 : 216 000 / 1 709 200 / 15.54%
07/2016 : 223 200 / 1 932 400 / 17.57%
08/2016 : 223 200 / 2 155 600 / 19.6%
09/2016 : 216 000 / 2 371 600 / 21.56%
10/2016 : 223 200 / 2 594 800 / 23.59%
11/2016 : 216 000 / 2 810 800 / 25.55%
12/2016 : 223 200 / 3 034 000 / 27.58%

01/2017 : 223 200 / 3 257 200 / 29.61%
02/2017 : 201 600 / 3 458 800 / 31.44%
03/2017 : 223 200 / 3 682 000 / 33.47%
04/2017 : 216 000 / 3 898 000 / 35.44%
05/2017 : 223 200 / 4 121 200 / 37.47%
06/2017 : 216 000 / 4 337 200 / 39.43%
07/2017 : 223 200 / 4 560 400 / 41.46%
08/2017 : 223 200 / 4 783 600 / 43.49%
09/2017 : 216 000 / 4 999 600 / 45.45%
10/2017 : 223 200 / 5 222 800 / 47.48%
11/2017 : 216 000 / 5 438 800 / 49.44%
12/2017 : 223 200 / 5 662 000 / 51.47%


We will suspend 540.000 FRN up to April 25th. In 4 months.

After this, 50% of the premined coins will be released. This will represent approximately 19-20% of the total coin supply.
Keep in mind the premine is shared between 4 holders. The resting 50% will be released next year.

I hold 20.000 FRN, and this was dedicated to the Paypal service which I'm in charge. I think I can lower it to 10.000 FRN. That should be enough untill April.

Now we'll check the most secure way to implement this.

Well that is not good, yo dev how are we standing with the exchange?

We're hearing what you guys say. We're day 2 and the premine is necessarily huge in comparison of the coins that have been mined. Though it would make absolutely no sense for the devs to sell anytime soon.

We're ready to escrow 50% of the premine up to next year. But if the process requires all trusted parties to confirm the sending of the funds then there's still a risk that one person will pull out and halt the process. Therefore I'm afraid we can not trust any person on this forum. We have to look at other possibilities.

Did you make any decision on that one? There is nothing to even think really I guess. Your coin will go to 1 satoshi due to the fear of anytime dump. And it will be very hard to restore the price after that. My two cents though, do as you wish.

It is a fresh one , dns is new . It came from France .
Here It work perfectly !
Thanks .

Hi everybody .

An explorer for Francs FRN is available here :

http://frn.altcoinexplorer.top/

Have a look .

Thanks.

I personally don't really know about this as I've never used it, but I'll pass the word and we will think about it.