Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - R

Pages: 1 ... 24 25 26 27 28 29 30 [31] 32 33 34 35 36 37 38 ... 68
451
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 16, 2019, 02:56:26 pm »
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?

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 😂

No, I'm hoping for improved documentation/support for private testnet faucet implmentation. Public testnet is not on the table for security research as it breaches HackTheDEX TOS.

452
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 16, 2019, 12:41:29 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 😂

453
Stakeholder Proposals / Re: [Worker] Reference faucet via BitShares.eu
« on: January 14, 2019, 12:20:58 pm »
Could this worker help with this issue? https://github.com/bitshares/bitshares-ui/issues/1773

454
General Discussion / Re: accidentally sent 10000 BitCNY to death account
« on: January 11, 2019, 01:10:29 pm »
It's impossible, consider the tokens destroyed. Any attempt at centralized theft of bitCNY destroys the credibility of bitCNY.

455
General Discussion / Re: New BTC Gateway - XOVBTC
« on: January 05, 2019, 11:00:48 pm »
Are you ok with users using your XOVBTC as backing collateral for bitassets on the BTS DEX?

456
Isn't 'recolatteralization' more the responsibility of the committee (since they're the asset owner) and traders (since they can bid on collateral & buy BTS on external exchanges) rather than witnesses? I don't want fake price feeds, stick to the BSIP-0018 recovery process.

457
General Discussion / Re: [ANN] Payger - Payment + Messenger
« on: January 04, 2019, 02:19:14 pm »
Do you plan on adding RUDEX UIA (exchange backed assets like RUDEX.GRC) support to Payger in the future? I massively appreciate the addition of OPEN.GRC, however OL has had this EBA on hold (suspended deposits/withdrawals) since early 2017 where as RUDEX.GRC has active deposits/withdrawals. OPEN.GRC did survive the most recent delisting wave: https://dex.openledger.io/news/announcement-gateways-openledger-dex/

Where Payger could fit into the Gridcoin ecosystem is within a theoretical commercialized BOINC project. BOINC projects perform volunteer distributed computing, by adding a paywall and a generic compute task submission process, one could spin up cloud computing businesses (offering compute in return for crypto) with effectively free computing power to compete against Golem, iEXc, sonm, and traditional cloud VPS businesses. The changes could take place within the existing (decades old) BOINC web server code which is programmed mostly in PHP and C++.

Keep up the good work though guys, it was great meeting you all in person at bitfest 👍

458
Bump. Waiting on payout from HTD WP for 3 reported issues. Anyone else submitted anything?


459
General Discussion / Re: would you support a cheater as the wintess?
« on: December 28, 2018, 02:02:36 pm »
Does not publishing price feeds for 'private bitassets' count as cheating? 🤔

460
The first DEXBot WP was pretty good though I felt its progress was slow towards the end. It'd be great if you could implement a bitasset borrowing bot, and enable one account to have multiple workers as this was possible using older bitshares market making bot software

461
I can't see the images, can you use an international image host like imgur please?

462
General Discussion / Re: Why the BTS network status is so bad these days?
« on: December 20, 2018, 02:35:50 pm »
the team need to be responsable for the whole development process include management / design / implement / test.
now all I can see is several unusable "stable" release, and seems nobody can tell me which one is the really stable/usable version.
Rewarding testing/bug-reports is out of scope of the ui workers, avoid 'release candidate' or 'staging' releases if you're only wanting to run 'stable/usable' versions. You should most certainly be updating your UI to the latest stable whenever possible otherwise you're a target.

463
What the heck are you talking about? Could you please explain in clearer words?
Also, please don't swear ..
Now, some whales do not produce bitcny, oppose bsip41 and bsip42, and prevent other users from producing bitcny
Nobody is preventing you from borrowing bitCNY, the only time this would be the case is if there was a global settlement for bitCNY. Why don't you borrow the bitCNY into existence yourself or enable your customers to borrow CNY using BTS if that's your business model?

464
General Discussion / Re: Bitcny acceptance business has been paralyzed
« on: December 20, 2018, 01:57:34 pm »
Can you elaborate please?

465
Stakeholder Proposals / Re: [New BSIP] Sharedrop Operation
« on: December 19, 2018, 06:47:47 pm »
BSIP-0023 is somewhat relevant, however it focuses on external cryptocurrency snapshots: https://github.com/bitshares/bsips/blob/master/bsip-0023.md

Several of the bitcoin forks have market caps 10x BTS, a single UIA worth billions could justify sharedrop BSIP research 👌
@Customminer, we do not currently see a Use Case for this particular BSIP.
If you have one in mind, please share with the community and let's talk!
Sorry, I will vote for no until these wrong feed price been voted out.
I don't think witness should execute it until it become an active worker.

What do price feeds matter when it comes to worker proposals entirely unrelated to price feeds? Don't stagnate BTS' development over broken bitassets.

Pages: 1 ... 24 25 26 27 28 29 30 [31] 32 33 34 35 36 37 38 ... 68