myyuxuan
|
|
September 23, 2014, 12:28:38 AM |
|
use DPOS as btsx?
|
We are the first!--DACRS (Distributed Autonomous Corporations RuntimeSystem)+dsKYEj7rMxGw151ab4YGhfhiBAXq1aSna6Get Free VpnCoin, Join BitNet ! Vy8GzHu8x95cwHBrtsB2bRbrWQW4ApjZ2y BitNet(VPNCOIN)第二论赠币:Vy8GzHu8x95cwHBrtsB2bRbrWQW4ApjZ2y
|
|
|
|
|
|
The block chain is the main innovation of Bitcoin. It is the
first distributed timestamping system.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
ownerbest
|
|
September 23, 2014, 12:53:01 AM |
|
use DPOS as btsx?
Please do not do this. DPOS is bullshit.
|
|
|
|
NxtChg (OP)
|
|
September 23, 2014, 08:24:27 AM |
|
DPOS is bullshit.
Why? The problem with PoS systems is that not enough stake is securing the system, which makes attacks easier. When you switch from flat to hierarchical model, i.e. from "everyone is a node" to "a bunch of master nodes", the problem becomes more severe. In case of btsx they have a fixed number of nodes, 101, right? Delegated PoS allows you to increase the stake of nodes. Now, I am not convinced yet, because when you lend your money with almost no consequences for you, there's no guarantee that an attacker won't be able to trick you to lend him your stake. So attacks might actually become easier in DPoS. You can probably verify that all of the nodes are honest when you have 101 of them, and that's the road btsx took. But small number of master nodes makes you extremely vulnerable to DDoS (which are quite cheap nowadays). I've considered DPoS several times. Maybe we can find some better solution to increase the size of node's stake.
|
|
|
|
NxtChg (OP)
|
|
September 28, 2014, 02:11:52 PM |
|
Progress reportThis week I was working on refactoring the bootstrapping protocol and unifying node and client bootstrapping. Since I lost about 2 weeks in September and also did some client refactoring, which wasn't planned, the core release is moved to somewhere in October. Hopefully
|
|
|
|
freigeist
|
|
September 29, 2014, 03:56:13 PM |
|
Progress reportThis week I was working on refactoring the bootstrapping protocol and unifying node and client bootstrapping. Since I lost about 2 weeks in September and also did some client refactoring, which wasn't planned, the core release is moved to somewhere in October. Hopefully Nevermind! Thanks for the update! Do what you have to do you know the best!
|
|
|
|
NxtChg (OP)
|
|
September 30, 2014, 10:08:49 AM Last edit: September 30, 2014, 10:35:52 AM by NxtChg |
|
Not to bash the Crypti team, but as I understand the main network is offline for 4-5 days already? Was it worth it to rush things? The issue is, you can't test for everyones varying hardware setups, network connections, or delays in requests and that makes getting all of the requests and consensus difficult to map out. Our system worked perfectly when scaled on 50 nodes running on different hosting platforms and our scaling projections appeared as though it would work up to 10s of thousands of nodes with no problem.
And then we launched. The system actually worked quite well at first but once the nodes started to climb and we started to see people running them in very different locations and sometimes improperly setup on different hardware and connection speeds which caused unforeseen bugs to pop up. We also saw several attacks on the network in just the short time it has been around. We saw malformed packets, DDoS attacks on nodes, as well as people sending fake requests, or at least, what to the network looked like fake requests. These various aspects were hitting the fork processing so often that the network was starting to skip blocks and hit 2 minute, sometimes 3 minute block times. Over time, it was causing the network to stop. This is unacceptable so changes needed to be made.
Bottom line is, you can't prepare for every possible occurrence and these are growing pains that Bitcoin and NXT both saw in the early days. They saw multiple attacks and even rolled back their block chains multiple times throughout their early days.
Keep in mind, we have posted an entire write-up on how the system is meant to work. You are more than welcome to try to "restart" and come up with a solution. We are always open to input from the community. The problem is that in order to use node-uptime as a property in our system, all nodes must send out requests saying they are alive with specific information and those requests must all get accepted and confirmed through the network with consensus and must do it in a 60 second timeframe. If you have any idea what that means, it's not an easy task, especially when you start incorporating slow connections, systems with different time settings (which we saw when we added windows), and attacks on nodes disrupting the entire system.
These guys couldn't do it in 60 seconds, I am trying to do it in under one. Now you can appreciate the difficulty of the task a bit better. Also, seems like I am right putting a lot of thoughts into DDoS mitigation, possible attack vectors, general reliability, etc. This is no joke. By the way, what a lame excuse: "What? Internet connections can be slow? Uh, we didn't know..." Anyway, I like Crypti and wish them well. Hopefully they will fix it soon.
|
|
|
|
NxtChg (OP)
|
|
October 05, 2014, 12:12:44 PM |
|
Progress reportNot much to report, because I am currently mostly working on many small things, instead of adding major features. -- Replaced the ugly "busy" screen in the client with a nice, embeddable progress bar: -- Spent two and a half days (!) trying to track down the cause of a weird random crash in the client. The crash happened only occasionally when 2 exposed API functions were called from 2 JavaScript timers and only when they returned strings of significantly different lengths Couldn't use the debugger because it crashed as well – seems like using IE as an OLE object from one DLL inside another DLL, linked from main EXE, while exposing DLL's API functions to JavaScript timers via another OLE object, utterly confused it Anyway, as usual with memory corruption, had to follow several wrong trails before finally stumbling upon what seems to be the main problem: for some reason IE doesn't like when the arguments he passes to my Invoke() are converted in place with VariantChangeType(args->rgvarg, args->rgvarg, 0, VT_BSTR). At this point I envy Java and Node.js coin developers...
|
|
|
|
|
NxtChg (OP)
|
|
October 14, 2014, 09:08:42 AM Last edit: October 14, 2014, 09:25:30 AM by NxtChg |
|
Progress reportSorry, I was so booored! I work on Simcoin for weeks and weeks and it moves very slowly now. I just wanted to make something complete and working. Something, where I don't have to spend hours thinking about every new line of code. So I took a week off and m6915 and I made a simple multiplayer game on top of the Simcoin codebase Download the game here: https://simxchg.com/simgame.zip (Windows only, sorry) If you don't have an account – just type username and password, it will create one. For now you will play with monopoly money, but later you will be able to play with real simcoins. There can be max 4 players and up to 8 spectators. We only tested it with 2 players and it was fun! Let's see how it will work with more players. The rules are simple: you explode someone, you take their 100 simcoins. When you join the game or suicide, 100 simcoins will be deducted from your account and distributed over the playing field under the brick walls, as 10+10+10+20+50 (displayed as (1), (2), (5) coins). Cursor keys to move, Spacebar to place the bomb, Enter to join the game.
|
|
|
|
lovely89
|
|
October 14, 2014, 09:25:36 AM |
|
Progress reportSorry, I was so booored! I work on Simcoin for weeks and weeks and it moves very slowly now. I just wanted to make something complete and working. Something, where I don't have to spend hours thinking about every new line of code. So I took a week off and m6915 and I made a simple multiplayer game on top of the Simcoin codebase Download the game here: https://simxchg.com/simgame.zipIf you don't have an account – just type username and password, it will create one. For now you will play with monopoly money, but later you will be able to play with real simcoins. There can be max 4 players and up to 8 spectators. We only tested it with 2 players and it was fun! Let's see how it will work with more players. The rules are simple: you explode someone, you take their 100 simcoins. When you join the game or suicide, 100 simcoins will be deducted from your account and distributed over the playing field under the brick walls, as 10+10+10+20+50 (displayed as (1), (2), (5) coins). Cursor keys to move, Spacebar to place the bomb, Enter to join the game. Sick. Will start practicing to rape some noobs
|
Bitrated user: vanlovely.
|
|
|
NxtChg (OP)
|
|
October 14, 2014, 04:35:12 PM |
|
How about this for a slogan: "Our coin is so fast, we built a multiplayer game on top of its codebase."
|
|
|
|
Nxtblg
Legendary
Offline
Activity: 924
Merit: 1000
|
|
October 14, 2014, 09:26:32 PM |
|
Progress reportSorry, I was so booored! I work on Simcoin for weeks and weeks and it moves very slowly now. I just wanted to make something complete and working. Something, where I don't have to spend hours thinking about every new line of code. So I took a week off and m6915 and I made a simple multiplayer game on top of the Simcoin codebase Download the game here: https://simxchg.com/simgame.zip (Windows only, sorry) If you don't have an account – just type username and password, it will create one. For now you will play with monopoly money, but later you will be able to play with real simcoins. There can be max 4 players and up to 8 spectators. We only tested it with 2 players and it was fun! Let's see how it will work with more players. The rules are simple: you explode someone, you take their 100 simcoins. When you join the game or suicide, 100 simcoins will be deducted from your account and distributed over the playing field under the brick walls, as 10+10+10+20+50 (displayed as (1), (2), (5) coins). Cursor keys to move, Spacebar to place the bomb, Enter to join the game. Nice!!!
|
|
|
|
alope
|
|
October 17, 2014, 03:12:36 AM |
|
How about this for a slogan: "Our coin is so fast, we built a multiplayer game on top of its codebase."Yep! Simcoin is a lightspeed payment!
|
|
|
|
ownerbest
|
|
October 17, 2014, 05:58:04 AM |
|
Progress reportSorry, I was so booored! I work on Simcoin for weeks and weeks and it moves very slowly now. I just wanted to make something complete and working. Something, where I don't have to spend hours thinking about every new line of code. So I took a week off and m6915 and I made a simple multiplayer game on top of the Simcoin codebase Download the game here: https://simxchg.com/simgame.zip (Windows only, sorry) If you don't have an account – just type username and password, it will create one. For now you will play with monopoly money, but later you will be able to play with real simcoins. There can be max 4 players and up to 8 spectators. We only tested it with 2 players and it was fun! Let's see how it will work with more players. The rules are simple: you explode someone, you take their 100 simcoins. When you join the game or suicide, 100 simcoins will be deducted from your account and distributed over the playing field under the brick walls, as 10+10+10+20+50 (displayed as (1), (2), (5) coins). Cursor keys to move, Spacebar to place the bomb, Enter to join the game. The Young at Heart
|
|
|
|
NxtChg (OP)
|
|
October 19, 2014, 07:44:11 AM |
|
Progress reportSince Simcoin is not yet finished, I've decided to make the game available to play with Bitcoin for now. So this week was spent finalizing the game, creating a database and integrating deposit/withdrawal method. This time withdrawals will be automatic too, so I don't have to spend time processing them. Rented a dedicated server in the Netherlands, so it's fair to both US and Asia and the game works much faster now. The official announcement will be in a couple of days, because some work still needs to be done. By the way, working on this game is not a complete waste of time It's built on top of the Simcoin codebase, so many bug fixes and improvements are directly mirrored to Simcoin.
|
|
|
|
marek3ball-orig
Member
Offline
Activity: 80
Merit: 10
|
|
October 19, 2014, 12:45:19 PM |
|
Nice work! Sliding around corners was more player friendly in the original game.
|
|
|
|
NxtChg (OP)
|
|
October 19, 2014, 01:25:33 PM |
|
Sliding around corners was more player friendly in the original game.
It works exactly as the original. Probably feels worse, because the frame rate is less and lag is too high. The newer version should be smoother and I also plan to improve this further some time in the future. It also helps to play at a higher zoom level, so hand-eye coordination is easier. The new version will have 100%, 125% and 150% zoom.
|
|
|
|
NxtChg (OP)
|
|
October 23, 2014, 01:38:46 PM |
|
|
|
|
|
NxtChg (OP)
|
|
October 26, 2014, 09:55:51 AM |
|
Progress reportThe CryptoMan game is working and people are starting to play it, which is nice. At least you can now see that I can deliver something working Most of the week spent finalizing the game, but I slowly started to code things for Simcoin again too, and plan to switch back full-time on Monday, so don't sell your IPO stake just yet
|
|
|
|
rlh
|
|
October 29, 2014, 06:07:51 PM |
|
What is the payload size of an average transaction?
|
A Personal Quote on BTT from 2011: "I'd be willing to make a moderate "investment" if the value of the BTC went below $2.00. Otherwise I'll just have to live with my 5 BTC and be happy. :/" ...sigh. If only I knew.
|
|
|
|