yanmaani
yanmaani
@domob1812 Any ideas?
Okay, let's go. This is ready for review. @domob1812
Thanks for all your review Daniel! I agree very strongly with everything you have said about delegation. I think the current situation is really hacky and frankly the code I...
I'm not so bullish on this. It feels odd to put this logic in name_show, and the point estimate for expiration is unlikely to be *that* useful. I'd rather have...
> @yanmaani Trying to use any kind of statistical model seems like over-engineering. Are there any real-world use cases where users really want to know what the nth percentile date...
I could tolerate a softfork that prohibited other than the owner from registering a name within 8.3 months of registration, or however long the average time is. But this? A...
> > to see when a given transaction will have N confirmations > > ...why do Bitcoin users need to care about this? To see when a transaction will have...
Okay, probably the Erlang distribution thing is overkill, but I still think that this should be a separate RPC. Ideally one that just gives you a point estimate for when...
No, the RPC really would be that short. I think name_show already provides the registration height, so all you'd have to do is calculate `NameExpirationDepth(height)`. I just think that this...
There is a ugly fix that you could do. If you ask very nicely, they might go along with it: ``` #ifdef UNIVALUE_ENABLE_UTF8_VALIDATION bool IsValidUtf8String(const std::string& str) { //... }...