- GetChains
It is, IMO, sort of the "missing link" in the common rpc command set for doing any sort of double spend checks.
Topic: [ANN][MOTO] Motocoin - page 54. (Read 178257 times)
It is, IMO, sort of the "missing link" in the common rpc command set for doing any sort of double spend checks.
when we hit the ltc coin caps
What does that mean?Although ltc could stand for something else.
I'm referring to this
Code:
/** No amount larger than this (in satoshi) is valid */
static const int64 MAX_MONEY = 84000000 * COIN; // Motocoin-FIXME: max amount
inline bool MoneyRange(int64 nValue) { return (nValue >= 0 && nValue <= MAX_MONEY); }
This section of code (and some related control flow changes elsewhere, also) affects, in relatively small ways, things like fee calculation, transaction validity, network work statistics, and more. They are all minor problems, but a lot of the things that "just don't work quite right" in the wallet/daemon (and in particular the rpc commands) hit this particular group of changes relative to upstream Litecoin.
(EDIT: I should also point out that the set of things that don't quite work right increases quite a bit if you do something like give yourself 100million coins on a testnet!)
When will you release the compiled client with
I don't think it is my place to release reference client builds, so for now I'll defer to WIlliam on this. Right now the patches are not entirely broadcast quality, but they are not far off. I've made a few more tweaks and will push a new set of patches out shortly, after I clean a few things up with the last merge..
Once there is a patch set that everyone seems happy to go ahead with, I'll be calling for all of the bot operators to make the switch at around the same time. Although I would think it likely that the majority of the miners will adopt the changes outright, some might disagree with the changes and may try to "vote against" the soft fork. Possibly some might even try to apply the attack vector "post mortem" and warp the old-rules branch to keep it perpetually longer (even after it would not be accepted as valid by the majority of the upgraded network) to confuse/trick old clients. This is why I think we would be wise to bump version number in block header soon, so users who are not following the situation get prompted to upgrade. If this is a particularly serious concern to anyone, we can enforce a hard fork, but I don't think the user-base is likely large enough to really necessitate it.
Right now there are a few issues with the total subsidy. There are quite a few "motocoin TODO" notes around the source related to it. Personally I think we should actually cap total supply, but this would need discussion.
Right now there are a few issues with the total subsidy. There are quite a few "motocoin TODO" notes around the source related to it. Personally I think we should actually cap total supply, but this would need discussion.
Any doubts? Really? This is the must for real crypto. Please, respect our prothet (Satoshi) and cap the total supply.
- GetChains
when we hit the ltc coin caps
What does that mean?Although ltc could stand for something else.
When will you release the compiled client with
You included bignum.h in moto-engine-cpp, game now becomes depended on boost and openssl. How were you able to compile it if makefile isn't changed? Compiling for windows will become much more complicated with such dependencies.
EDIT: It isn't actually used so I just commented it out.
EDIT: It isn't actually used so I just commented it out.
Probably I messed something up in the merge. I was in a hurry when I pushed it.
Quote
EDIT2: Generated maps are good but still not anywhere near human mineability.
I just meant that it had some small parameter tweaking to make it generate better maps than what it searches with the bots. Human mining will not really be able to become approached by most humans (except the most skilled and dedicated) until we do something like the "N heads" concept. Interestingly the way I am bot mining now there is actually an optional human mining element to operating the bots, where you can help nudge your bots along at your discretion. This makes for a fun sort of meta game in the mean time.
You included bignum.h in moto-engine-cpp, game now becomes depended on boost and openssl. How were you able to compile it if makefile isn't changed? Compiling for windows will become much more complicated with such dependencies.
EDIT: It isn't actually used so I just commented it out.
EDIT2: Generated maps are good but still not anywhere near human mineability.
EDIT: It isn't actually used so I just commented it out.
EDIT2: Generated maps are good but still not anywhere near human mineability.
Right now there are a few issues with the total subsidy. There are quite a few "motocoin TODO" notes around the source related to it. Personally I think we should actually cap total supply, but this would need discussion.
I don't see any issues.We'll come back to it. It isn't anything critical or that has much impact on protocol, but some other functions of the wallet fail for related reasons like progress/lnwork calculations. In any case, I think we should have a finite cap, otherwise we might be particularly susceptible to 'mudconomic' effects. There are a couple of ways that we can make a finite supply without ending up in a "wait around for a block to compete just on tx fees" situation.
Quote
I merged your pathes. I don't have much time to fully review them, do you think that new version can be released as is?
It could, but the warp fix is still conditional to testnet and the map filter should probably be made optional with a key binding or something. I'll further polish the changes as I have time available today/tomorrow.
EDIT: Also the second (and more useful) part of the getchains patch got missed in the merge. I'll push this in a bit as well.
Quote
EDIT: where is "game/debug.h"?
HEH, I hope this doesn't become a running joke with moto. It got stuck into different commit than what got merged, for silly reasons. You can grab it from m1ner's fork and I'll also push it to my master when I get back to a real PC.
Right now there are a few issues with the total subsidy. There are quite a few "motocoin TODO" notes around the source related to it. Personally I think we should actually cap total supply, but this would need discussion.
I don't see any issues.I merged your pathes. I don't have much time to fully review them, do you think that new version can be released as is?
EDIT: where is "game/debug.h"?
@WilliamLie, if I pullreq these patches (with TwoTargets enabled for live net) do you think that you'd merge them? I think the soft fork for the fix will likely go much more smoothly if we're not forced into "forking against" the reference client.
Most probably, I just need to look at them.Ok, https://github.com/HunterMinerCrafter/motocoin/commits/master most of them are up. I need to rework a few minor things with the testnet and ltc backports a bit, but I'll get them up today as well.
The most recent commit there is entirely untested so far, heh.
improving the game physics
What for? I think that bots don't care.Sure, but humans care. I've had multiple people mention that the physics feel off.
when we hit the ltc coin caps
What does that mean?Right now there are a few issues with the total subsidy. There are quite a few "motocoin TODO" notes around the source related to it. Personally I think we should actually cap total supply, but this would need discussion.
@WilliamLie, if I pullreq these patches (with TwoTargets enabled for live net) do you think that you'd merge them? I think the soft fork for the fix will likely go much more smoothly if we're not forced into "forking against" the reference client.
Most probably, I just need to look at them.improving the game physics
What for? I think that bots don't care.when we hit the ltc coin caps
What does that mean?
Sounds great! So, we gotta wait for the merge?
So, how's the patch coming along?
Well, I was hoping to get some more feedback/criticism/comments on the gist outline, but this doesn't seem to be happening.
I've been preparing a proposal release. I have had a build of it running/mining on the real chain for a couple of days now, and it seems stable. It has the following "feature branches" included so far:
- TwoTargets
- GetChains
- MoreWarp
- MapSeeker
- TxReplay
- TestnetBox
- LtcUpdates
I'll push these branches to my github today for more people to try. I think whether the others step in with feedback on the patch or not we should go forward with launching the change as a community, and make improvements later. IMO, it is important to at least address the attack vector with "something" ASAP, even if that something is not the ideal. Worst case we end up having to hard fork after all, but I see this as an unlikely outcome.
I also have Minim1ner's full bot cleanly merged in, tweaked/optimized, and using the original wallet's build files so it builds cleanly/easily on windos and *nix. I'm assuming OSX will build with the other pullreq that is hanging out there, but I can't test it as all of my mac hw runs linux. However, these patches won't be released until after some fix for the warp is adopted by the network.
@WilliamLie, if I pullreq these patches (with TwoTargets enabled for live net) do you think that you'd merge them? I think the soft fork for the fix will likely go much more smoothly if we're not forced into "forking against" the reference client.
In the future, after the warp attack issue shakes out, I'd like to work on improving the game physics, addressing the question(s) of what happens when we hit the ltc coin caps, and adding some more interesting elements to the competitive aspects.
The buy side doesn't look too optimistic eh.
You can say that again.It looks like it was mostly a single seller dumping into a thin market on low volume. Buoyancy in response is quite low, however.
Interestingly, network hashrate and market price seem less coupled than with many other coins, so far.
So, how's the patch coming along?
The buy side doesn't look too optimistic eh.
You can say that again.
The buy side doesn't look too optimistic eh.
Still cheap on C-Cex!
Looks interesting.