If the rule is set and the ToS updated, then that means public battle helpers will most likely stop their service, even if nothing is enforced. Which means that private ones will dominate. Please dave,

All this will do is disallow the public from using battle helpers. Those at the top will keep on using their private solutions and dominate everything. That's also my concern. I understand that BH can

You didn't go into any of my questions, instead you're trying to bring some argument about Matt being "my boss". I respect Matt and his judgment, but this is my account and I'll write whatever

the use of professional services as well as sharing of spreadsheets, data bases, and match algorithms between users. When is a spreadsheet/database illegal? How much data must it contain? How good does

First of, I appreciate the initial idea! My main concerns about this proposal is the required work involved to do the trades. When I heard about the idea that a DAO representative should do this, I've

Thanks for the proposal, Matt. I support the primary idea behind it. But, I think the price is too high. 25k DEC, at peg 25$, would put a GFL at around 70% cost of the cheapest non-soulbound CL GFL (35$).

No, absurd is arguing against a clever use-case for SPS that was also described in the whitepaper. SPS is at 2 cents, many people bought when it was 5x higher or more. You're getting a massive discount.

Did you ever use a battle-helper? If yes, how was your experience when changing the proposed matchups?

It will morph into battle-helpers. Don't kid yourself. It might sound nice, it might give you a cozy feeling of "finally we'll do something about bots", but since we can't enforce anti-battle

The reward pool would be split in 2 (besides Wild/Modern), thus nerfing the rewards per battle. Additionally, the team would have to shift time from adding new features to trying to implement anti-bot

The proposal could be a reason for people to get incentivised to claim their deeds, thus speeding up the process. Though I'd argue that the 60 days drop-off for the starter packages is also an incentive.

Of course! Refund was sent. Though I tested it myself and account creation worked fine. But it could have failed due to Hive nodes being a bit wonky recently.

Before trying to tackle bots one would need to ask the right questions beforehand and discuss this maybe with some folks who have some developing background to get at least an idea what could be a possible

Hey, so the popup is there to buy Credits, which you then can use afterwards to create the account. Can you check if you have enough Credits? Otherwise I'll refund it of course.

So there are two options: 1.) You could fetch multiple blocks at the same time. (Promise.all) 2.) You run your own HiveEngine node. I haven't done that for Hive Engine nodes but in regards to Hive RPC

No, it's a library. A developer uses this as part of a website.

Hey, so basically dhive-sl is an easy way to interact with Hive via the programming language Javascript/Typescript. While this was of course previously possible, I've made some improvements for more features

Nice! Note that dhive bundled all of the dependencies and native code into a single js file, while dhive-sl doesn't, thus dependencies that dhive-sl relies on aren't included in dhive-sl.esm.js. But those

Hey, a solution is to add the following code to your nuxt config build: { transpile: [ ... 'dhive-sl', ], }