Can someone explain why I harvest blocks and get 0 fee?
If there are no tx in a block then there are no fees and therefore no reward. 0 inflation does have it's drawbacks I'm afraid. |
|
|
|
Looks like we will be dropping into the 30's sat range soon.
in 1 month the price is 30 sat. in 2 months the price is 20 sat. in 3 months the price is 10 - 5 sat. in 4 months the price is 3 - 1 sat. at such future price in 1 - 3 sat could make at once 888 trillion coins to begin with the price in 1 sat. that raise XEM of the beginnings it has to reach at the beginning a bottom in 1 sat. Keep dreaming  At 1 sat one person could buy all NEM around, not gonna hapen... Price is only important for the weak hands and speculators who intend to sell anyway, we don't need them i will wait price 1 sat in next 5 - 6 months. hey look at volume xem is die! very eloquently put. Thanks for sharing your predictions. |
|
|
|
There are no blocks as Fuserleer said, so I assumed there was no blockchain reorgs. A ledger can't accept a double-spending transaction without doing a reorg.
This is true. However, the only way to have no forks is to know in advance (and forever) who the nodes building the ledger are - in that case, if, say a network split occurs, the nodes who split off will lose connection to the ledger production nodes and simply stop with a 'no consensus' result. But if your list is arbitrary and constantly changing, then forks are inevitable. Maybe we should all just wait for the ledger discription. There are no blocks but there has to be someway for reorgnaizations right? The primer itself says that all nodes are not always in the exact same state (for legitimate reasons). So there has to be a way for them to agree on states (which afaik is the transaction consensus value) and to change their own state in case it turns out someone else has a "better" state. |
|
|
|
So let's see if I understand this.
Nodes build trust. With that trust they can - simply put - vote on transactions by countersigning them which gives the transactions consensus value. When nodes sync with each other they don't pcik the longest chain like in bitcoin but they pick the chain with the highest concesus value i.e. the chain that most trusted nodes signed.
Is that about right ?
For the purpose of understanding trust consensus you do not need information about the ledger or how it is constructed. There is no chain as specified in the document, there are no blocks either. Transaction are validated and committed individually in real time. The ledger is 100% different from Bitcoin and everything else. If me and you both submit a transaction 10 seconds apart, then mine will be committed and final around 10 seconds after yours. There is a record of all transactions though right ? And nodes do agree on that record right ? |
|
|
|
|
So let's see if I understand this.
Nodes build trust. With that trust they can - simply put - vote on transactions by countersigning them which gives the transactions consensus value. When nodes sync with each other they don't pcik the longest chain like in bitcoin but they pick the chain with the highest concesus value i.e. the chain that most trusted nodes signed.
Is that about right ?
|
|
|
|
Could explain how trust is formed on a network level and not on a node level ?
As far as I understood nodes send challegens and if those are answered correctly the node on the other end will gain a little trust. But that trust would only be for the challenging node as he sent the challenge right ? How is that experience brought to a network leve ? Does the simply broadcrast to the network that he received a valid result for a challegen from node x ?
Sure, maybe a simple example will help. Lets assume there are only 3 nodes in the network, A is you, B is me, and C is someone else and is currently offline. A & B are connected in the network, and have been sending challenges to each other periodically. B wants to send a transaction to somebody, and as it is only connected to A, it endorses A for any work done and for passing the challenges, and sends the transaction. This endorsement is recorded in the transaction directly, remember that. C now comes online, synchronizes and connects to A. C is curious if A is trusted, so scans the transactions for any endorsements that reference A's SNID. C will see the recent endorsement of B -> A and any others that have been made in the past, and can easily calculate A's trust level from the endorsement information in transactions. (Note: C will not be able to discover who endorsed A, that information is not recorded) Transactions are stored in a public ledger just as in BTC and other cryptos, and endorsements are not encrypted or masked in any way. Therefore everyone can see at any moment, who has been endorsed and calculate their trust level and compare it should they wish to any other trust level. Does that help to understand it? So basically trust is "credited" on the ledger and there for everyone to see. Thanks for clearing that up. |
|
|
|
Sorry if this has already been asked but what would stop any plattform from having "centralized app utilizing blockchains" ? Shouldn't this just be green for all of them ? Or is this to merely point out the existence of such services ? Even if so...they all have block explorers, faucets or whatever  |
|
|
|
|
Could explain how trust is formed on a network level and not on a node level ?
As far as I understood nodes send challegens and if those are answered correctly the node on the other end will gain a little trust. But that trust would only be for the challenging node as he sent the challenge right ? How is that experience brought to a network leve ? Does the simply broadcrast to the network that he received a valid result for a challegen from node x ?
|
|
|
|
What are you talking about, nem.io is not empty  open other web sites and you will see a difference as there at them the first homepage is issued and as it is issued at NEM. https://www.stellar.orghttps://ethereum.orgunless it isn't visible as there at them the first homepage is filled with the description of useful functions and NEM on the first homepage don't have anything. where the description of that that is multi-signatures? where about that that NEM possesses innovative and best block chain? where all that has to be as descriptions and advantages shown on pictures in comparison with other block chain crypto platforms? therefore also the potential investor going to the homepage NEM sees anything and leaves. therefore he also considers NEM a usual simple coin as on the homepage to it all essence doesn't reveal at once. for search of an essence it is necessary to spend an extra time and to go in I undressed the blog. on it the potential investor has no time and without having taken away any advantages on the homepage he leaves on farther from NEM. not surprisingly why the price of XEM constantly falls and all investors consider XEM a dead coin. notice - a coin. i.e. they don't even know what is it because as the same Stellar and Ethereum has no detailed description in pictures that such NEM and in what its advantage in comparison with other block chain crypto platforms of new generation. Literally the first thing you see on the website is a video explaining NEM. If people are still intersted after that they can find pretty much everything on that website (except links to the community which has been debated). If you got clear, concrete suggestions please go ahead and make them. |
|
|
|
i wanted update servers but https://forum.ournem.com is down. THere were guides how setup VPS for NEM i have used them, without those guides (*rather scripts i am done ) that 0.6.31 will stay till free amazon time is over. it is easy to change *31 to *43 but clear guide is not avaible right now so i gave up till forum is up again. or you canpaste me few command lines how easy update it by command line (like for noob) All guides can (afaik) always be found here http://blog.nem.io/nem-tutorial-list/ |
|
|
|
What caused the price drop?
BTC went doesn and everything follows. Not exactly a new paradigm. |
|
|
|
*removed img for space* Very nice graphic and easy to understand. I think a lot of these graphics programs can be downloaded for free on Google but the trouble isn't making them but making an informed and correct comparison between NEM and another project. https://bitcointalk.org/index.php?topic=1153740.0Most of us need threads like the above and hope the information about the other projects are correct. Thank you! It isn't that easy as you think btw application can work in stealth mode
I can't understand what does it means Actually Lon gave me some feedback @ Telegram on the info graphic and here is his reply to my same question: If you understand tiered architecture design, applications can all hide behind a firewall and talk to any NIS. Hence it is masked. It is hard, but not impossible for anyone to track where the application solution is coming from. This method of design is commonly known as stealth mode. From security standpoint, you don't need expensive security solutions to run this sort of set up. It saves a lot of money on both hardware and software. Programming in terms of hardening the solution is also made simpler. Hacking is very much reduced to insider job, which is very much the same as many solutions with hardened security. ... Wuut ? Could you elaborate on why it's hard to track where it's coming from and why this is so secure ? Something else I noticed. The graphic says that the most active nodes are being rewarded. This is incorrect. It should say the most active accounts are rewarded or rather more important. Lastly, imho wether NIS is run remote or local doesn't pertain to how "hot" the wallet is. btw did you make that graphic? Good job ! Looks really nice. |
|
|
|
For me it comes down to this: from the whitepaper 2. Lock Race Attack
In a lock race attack the sender forms two transactions and two locks and
submits one to the merchant and the other to the rest of the network. In this
case the locks will cancel each other out and the transaction MUST wait for
block inclusion before being considered confirmed.
The attack will NOT result in a double spend but it does force the receiver to wait for 1 confirmation. So I don't see how ZT solves anything if I should prob wait for 1 confirmation just to make sure. If the nodes are being chosen randomly - compared to instantx - then how is this not vulnderable to sybill attacks ? The more nodes I controll the more likely it becomes they are chosen. So I don't think it's random (allthough I don't see any quality assessment in the calculation of the voting score). I'm by no stretch an expert so could someone point out what exactly it is I'm missing ? You can hardly expect everyone having questions to go through all the code. |
|
|
|
Okay I've digested the white paper. I appreciate john-conner providing more details. That was the honorable and helpful action. Unfortunately afaics, there are elementary attack vectors that he has not addressed in this white paper: - No cost to being a peer, thus a Sybil attack on nodes in general. The adversary could insert a unlimited nodes if he wants to in order to dominate voting.
- How to squelch DoS attacks on the vote? A node which always votes against consensus can't be distinguished from one voting honestly since lock conflicts result in an indeterminate vote.
- He employs a Bellagio Algorithm to avoid gaming the selection of which nodes to poll for votes, so this removes the reputation weights of Skycoin's consensus, but it doesn't address the spamming of total node count nor the spamming of the lock conflict.
- Nodes are not paid for voting. If they receive bribes from the double-spender, the algorithm has no defense other than it hopes that 50% of the nodes in the network are not on-the-dole.
- Lock request spamming or DoS attacks. Are transaction fees hardcoded for the entire network?? Preset constants are anti-decentralization.
Also this algorithm requires the entire network to see all the transactions which of course won't scale without centralization, so if he is trying to enable real-time microtransactions (1 second confirmations) which could explode transaction volumes up to the 100,000s or more per second then he has a problem. Refer to the GavinCoin fork debate. He's solving Bitcoin problems thought impossible to solve while you are a troll on a forum.....hmmm who to trust. Even if he is a troll his questions make sense and should be answered. Also I could just always broadcast 2 Locks (Race Attack) and sometimes I'll get lucky (and the merchant unlucky) and other times the merchant will get lucky. It doesn't cost me anything so why not try ? So in the end the merchant should be waiting for the next block either way or am I missing something ? (Serious question not trying to hate) Is the only thing that seperates peers form super peers that peers aren't reachable and super peers are ? If so I find the naming very odd. |
|
|
|
Nice work !
Are you on telegram or slack already ? If not you should really join.
Never used both but I will join for sure ! Better slack or telegram ? I'm going for a little break and I'll get back to the faucet in some hours, once it's done I really want to work on XEMsign, it would be great to secure funds like, Dice funds Slack vs. Telegram has almost turned into a regligious question. I'm an advocat of slack because they don't ask for a phone-number and it's easy to integrate a ton of stuff (like the tipping bot that is already running there). btw. if you're so eager to code. The bots that are connecting telegram and slack could really use some work and I think they are written in js |
|
|
|
Good It also just occured to me that you should probably use a captcha and maybe we should block people indefinitely after 2 or 3 drips. I man a faucet is for people to check out NEM not to have a constant flow of XEM. Did the captcha also (I just need to change for Recaptcha). For blocking, if you want it, I can do it. The faucet core is ready and XEMbot can initiate batch multisignatures requests every x minutes for addresses meeting requirement. I can add a new counter for every claims from an address and block at n claims. Still the design to do, some little tests and it's good Nice work ! Are you on telegram or slack already ? If not you should really join. |
|
|
|
I suggest you use this https://github.com/Valve/fingerprintjs2 for the fingerprinting. It's a new release of what we adapted for the claiming portal (adapted to make it harder to change ones fingerprint). It is exactly what I used  Good It also just occured to me that you should probably use a captcha and maybe we should block people indefinitely after 2 or 3 drips. I man a faucet is for people to check out NEM not to have a constant flow of XEM. |
|
|
|
I can tell you are working hard!
It's really basic code and I'm having a lot of fun playing with the APIs Faucet is almost done, just need BrowserFingerPrinting, claiming parameters (chosen by the community) and some tests. Then you can review it and deploy it where you want I suggest you use this https://github.com/Valve/fingerprintjs2 for the fingerprinting. It's a new release of what we adapted for the claiming portal (adapted to make it harder to change ones fingerprint). |
|
|
|
XEMsign - Automated cosignature Written in JavaScript for NodeJs. Review, fork, use, improve => GitHubStill pretty basic code that needs lots of improvements but it does the job  You absolutely must know how to correctly use multi signatures accounts before use or your XEMs can be lost forever ! Does your software cosign every transaction it sees or is it possible to define some rules? It would be nice to have rules like: sign transactions up to 1000 XEM sign no more than 100 transactions per hour sign no more than 1 transaction per day to the same recipient address ... The readme on github states that there are already some rules. Obviously a lot more is possible. |
|
|
|
Few questions:
How many XEM would you like a faucet to give out ?
Do you want it instant or every n amount ?
How many time between claims ?
I think 1k to start with should be fine Within a couple of minutes I'd like to see the pending tx in my account Depensd on the amount. At 1k I'd say once every 48 hours. I'd also set a daily limit for the faucet as a whole. Say 100k. |
|
|
|
|
Show Posts
