Interesting ... they seem to not have done their homework about how to setup an instance in low-ram mode.

For commercial grade support, they can surely ask for a quote from info@blockchainprojectsbv.com
Or simply ask the community here - there are a bunch of knowledgeable people around

For your information:
The updated fee schedule proposal has been approved by committee
It will execute on 2019-02-15T11:08:38 and take effect on 2019-02-15T12:00:00

Dear community,

I just created a proposal for committee that expires in 2 weeks.
The proposal proposes to set the fees according to @clockworkgr results of business analysis.

The proposal has been discussed here:
https://github.com/bitshares/committee-tools/pull/2

The details of the fee schedule are here:
https://github.com/bitshares/committee-tools/blob/master/usd-denominated-fees/config.py

There were over 8 weeks since we first started discussions publicly here:
https://github.com/bitshares/committee-tools/pull/1

Details and reasoning for the proposed (USD) valued fees are here:
https://github.com/bitshares/committee-tools/files/2629094/2018-11-update-details.xlsx

As USD valuem the current feed price is taken.

I expect every committee member to either approve or provide an explanation (to the community) for not approving.

you are doing it wrong

https://xkcd.com/221/

I would like to bump this proposal in case people missed it.
This proposal was supposed to start fund ongoing operations of the faucet starting today.

The previous contract for operating onboarding.bitshares.foundation with the BBF has expired since the bitshares.ws infrastructure worker
has expired too.

Of course, the BitShares community is free to deploy their very own faucet somewhere. I merely offer to use BitShares.eu's redundant deployment including
detailed logging and reporting.

In the mean time, even though the worker is not yet approved, the faucet will operated as usual within a grace priod to give every BTS voter a chance to voice their opinion.

Cheers
 -- Fabian
     BitShares Europe

Thanks for setting up those workers!

Quote from: xeroc on January 16, 2019, 08:15:00 pm

if you use this repo:
https://github.com/bitshares/tapin

and point it to the testnet api (wss://node.testnet.bitshares.eu), it will setup a local faucet for testnet

For a private testnet?

For a private testnet, you need to add your chain id and prefix to
python-bitshares/bitsharesbase/chains.py

Else, the library will complain when connecting to an unknown network.

Testnet:
faucet: https://faucet.testnet.bitshares.eu
prefix: TEST

Mainnet:
faucet: https://faucet.bitshares.eu
prefix: BTS

If you send a public key with the wrong prefix to the faucets, they will raise an error/exception.
Is that what you are looking for?

Quote from: xeroc on January 14, 2019, 02:09:19 pm

Quote from: Customminer on January 14, 2019, 12:20:58 pm

Could this worker help with this issue? https://github.com/bitshares/bitshares-ui/issues/1773

BitShares.eu will give you a warning (that will show nicely in the UI) in case you try to create an account with keys for a different blockchain.
From a faucet POV, we can only identify "wrong blockchain" by means of the "prefix" (the first characters in your public key, e.g. BTSxxxxxxx).
If someone sets up a private blockchain and uses the same BTS prefix, then there is no way if knowing the users wants those accounts to be created somewhere else - in fact, the keys are identical then!

Could you help with the documentation aspect of private faucet & testnet setup please? I hadn't realized that you'd get an error if you changed the prefix, in my past security research I was blocked by an inability to use a private faucet on my private testnet :/ I've probably registered 10 accounts on the public testnet instead of the private testnet during early attempts 😂