6. What are your thoughts on passing out the stakes in 3 parts?
Everyone gets a third every 10 days?
Bad idea? Why?
Good? Tell why you agree?
I imagine distribution takes a long time because they do it manually. This would make it three times the work. |
|
|
|
So now i test, pc was in sleep modus, if i was working, and my local wallet still forging a block again in sleep modus, so IŽAM SURE it works, BUT WHY ?
If your computer is offline you are not forging, period. If your account are forging when your computer is off, I can only see two possibilities: 1. At some point you logged in to the web wallet ( https://wallet.fimk.fi:7886), and you are still forging there. 2. you are mistaken |
|
|
|
wow so many names that i recognize from nxt. i had no idea so many of you cool cats were involved over here as well.
Pretty much every PoS / IPO thread are full of ppl from nxt. We are the ones that know the PoS (or some variation) is the future, that just because it's an IPO, or a forum distribution it's not an automatic scam. And we also want to get luck (again).  |
|
|
|
|
My concern is that these endless issues are huge distractions. If devs are occupied with auction, auction overrun, puppet removal, and puppet removal consequences, then when do they have a time to code?
As long as Node is excellent, thinks can turn better, but if it can send and receive coins in a nxt clone client, no new and exciting functions, then this will turn ugly(er.)
|
|
|
|
I did leave but i came back to lol at the quote above about auction buyers. money allows you to cheat
This would be all right, if we could look at it, as a step after IPO and before active trading. NEM is also going to hold a (huge) auction, before launch. (Or they were planning to, I'm not following NEM actively.) The problem is, there was an auction... then talk about another auction. Then now this with puppets, no clear mechanism what happens to coins from puppets. It's a mess. As I said before, devs suck at this. One bad public relation decision after another. How did they think that doing puppet removal this way would not result in this war in the topic is a mystery to me. |
|
|
|
Skewing toward small stakeholders don't work. We ran these rounds with Nxt before.
It would take me about 5 minutes to write a scrypt that can distribute my account into 10k chunks.
I seriously doubt any big stakeholder would waste time doing this. If you really wanted to, then you could find a way to distribute to smaller stakeholders. I was talking about skewed distribution in general, and why won't it work. If we are still talking about the 10k rewards, I honestly don't care, and I don't even know why we are talking about it this much. It worth 0.03 BTC currently, less than 20 bucks. |
|
|
|
Skewing toward small stakeholders don't work. We ran these rounds with Nxt before.
It would take me about 5 minutes to write a scrypt that can distribute my account into 10k chunks.
BUT, they all would have to be forging too. That's the catch, isn't it. If even the need of active forging is not an issue, then it has to be something along these lines I suppose https://bitcointalk.org/index.php?topic=633304.msg7720567#msg7720567There is no cath, you can forge with as many account as you want on one node. There is no difference if you log in with one account or a 1000. |
|
|
|
Reward the first account whose balance is less than or equal to 1M FIM starting at block 10,000. That's an easy way to skew the rewards toward small stakeholders.
Give 50% to account at 10,000 (likely to be large stakeholder) and 50% to first small account following block 10,000 (guaranteed to be small stakeholder).
What prevents the large stakeholders from dividing their holdings to several smaller accounts, if we start to considerably favor small accounts? The annoyance just slows them down and wastes energy. I'm not sure how the math works, but will X amount of FIMK forge the same number of blocks split across multiple accounts as it will in a single account? Yes, same amount. But it would require huge amounts of accounts to be generated by big account-owner, 1800 accounts for that 18 million to take it down to 10000 balance each. I would not do it if I forged millions in a year anyway. Skewing toward small stakeholders don't work. We ran these rounds with Nxt before. It would take me about 5 minutes to write a scrypt that can distribute my account into 10k chunks. |
|
|
|
i agree 100%
the way crypto works in my eyes atm is still the same as fiat the rich get richer and the poor get fuck all lmao (yes i am in the poor section haha)
I really wish people would stop saying this, because it's just not true. The saying refers to systems where the rich gets better return for their money. Just because they have more they get more opportunities and favorable terms. You know, like the real word. But with PoS the rich do not get richer. No matter how much coin do you have, any one coin will always earn the same return. This is the most fair system you can ask for. |
|
|
|
Proof of work is not a financial instrument. Proof of stake means the holder gets paid additional stake for holding. Same as in a savings account.
The fact that this is a cryptocoin does not make any difference. It is a negotiable item, which earns interest, and is being sold by unregistered persons. It is no different than buying a bond.
PoS coins do no earn interest. None. What (potentially) earns you coin if you secure the network. To secure the network you have to have coin. There is no new coin introduced to the system, the already existing ones only get suffled around. I'm afraid the only place this resembles a behavior of a bond is in your head. |
|
|
|
I did, but I assumed that there would be mining after the IPO since you mentioned that only the GENESIS block was for sale in the IPO, and that 100 Million coins were the total. Your OP was not clear that the GENESIS block is the ONLY block
100% POS. It's in the topic subject... (and a million other places) |
|
|
|
Dance is right, the amount you see fits the order-of-magnitude you should be in. Also, you are forging with an effective balance, which only takes effect after 1440 blocks (after the transfer), and I see you did some transfers during the last few days.
If I do a transfer my forging stops and starts only after 1440 bloks. Did I understand it right? Yes. (But only for the coins you moved.) |
|
|
|
Initially, since this is an experiment as much as anything, I want the asset to have
a lifetime of 1 month from date of issue. Can I do this just by stating that's the deal
in the asset description?
You can do it, but you have to make it very clear to everyone, and set the price accordingly. (You could in theory buy back the asset shares at the end of the month, but it's not a good solution.) I don't think there were an asset so far that had a time limit. There is no way to destroy an asset. Especially shares that you sold to others. Question: Having issued the asset, by default I own the 1000 tlcMNT, and can then set an
ask price on the exchange?
Yes. All issued asset will be in your account and you can post ask orders, at any price. Question: the 1000NXT fee to list the asset - who/where does that money go to?
As any fees: to forgers. Whoever forges the block after you issued the asset gets the fee. |
|
|
|
Did you guys at least anonymize the IPs before storing them somewhere ? Like hash them or alike ?
Anything else would have been messed up imho (and actually illegal without any sort of EULA / Privacy statement).
Hence the reason they call it a secret method. But I have to give it to them, it's effective. |
|
|
|
How many people are disputing their sock puppet status? Not too many so for the ones who come forth with a dispute, im sure the devs can work something out (provided there is some proof as to the validity of the claim).
And I'd put money on it that he is lying his ass off. |
|
|
|
let's keep something in mind.. All members had to login to a central server to get their public key. they could have easily tracked ips, associated them to public key generation, and looked for single ips associated to multiple public keys on the member list.
having watched the nem sock puppet hunt, they may well have had the foresight to anticipate such a need.
Devs may be smarter than you think.
Yep, most likely. There is really no other way they can be this confident about some of the puppets. Live and learn, next time puppet masters will remember to use VPN. |
|
|
|
3) I donot think koop4u's screening way is good: you cannot make a judge just with your intuition or vague indications(like similar name) and without any directive proof!
4) koop4u: What you are doing is hurting the NODE communities' faith in your executive ability and reputation.
5) You should delete any information destroying my reputation. I retain my rights to report to the BTT supervisors to defend my reputation and to refund me.
hill
I really didn't want to get into this whole thing, but seriously? Rockhill used " donot" twice in his last few posts. I remember, because I found it unusual. He wanted to report to " BTT monitor", he was worried about his reputation, and wanted his stake returned. |
|
|
|
Not Nxt, but the coints that can be built on top of it. |
|
|
|
The easiest way would be to update the countdown on each block (a drawback would be that the time to forge will jump around constantly).
But since you need to send your secretPhrase along with the request for the deadline, making that automatic (without the users expressed consent) has the risk of a user on a public node sending his passphrase once. Then realizing he/she doesn't want/trust that and the client will continue doing so.
This is a first basic implementation of the forger countdown, I can imagine a next release to show the current behavior only when you are on a public node.
Honestly, I understand why do you display the countdown, but from experience with Nxt I think it just confuses newbees. How about instead of calling getForging you just make the calculations on the client side. Instead of a countdown you could just display the avarage forging time based on balance, coin supply, and last base target. It could be updated with every block. "You will forge a block an avarage of x weeks/days/hours", is good information, and less confusing than the countdown that jumps around and in no way accurate. Or if you love the countdown you could check last forged block time, make the above calculation in client, and create a countdown. This way there is no need for passhrase. |
|
|
|
You'd better use FIM wallet client rather than the web wallet.It's more safe.
That's what I'm saying. The sentence is confusing for ppl that are using local nodes, not a remote server. |
|
|
|
|
Show Posts
