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 - kimchi-king

Pages: 1 2 [3] 4
31
Stakeholder Proposals / Re: [Proxy] kimchi-king - Journal
« on: July 25, 2018, 03:18:33 pm »
I currently have 38 proxy followers which equates to 2,450,382 votes.

You can track this info in real-time here: https://www.cryptofresh.com/u/kimchi-king

32
Stakeholder Proposals / Re: [Proxy] kimchi-king - Journal
« on: July 25, 2018, 03:10:06 pm »
Here's a breakdown of my current votes.

Committee
bitcrab - Yes
abit - Yes
jademont - Yes
clockwork - Yes
witness.still - Yes
ebit - Yes
bhuz - Yes
xeroc - Yes
harvey-xts - Yes
bunkerchainlabs-com - Yes
openledgerdc - Yes
fav - Yes

Witnesses
in.abit - Yes
bhuz - Yes
abc123 - Yes
verbaltech2 - Yes
roelandp - Yes
witnes.still - Yes
xman - Yes
delegate-1.lafona - Yes
elmato - Yes
mglab - Yes
xeldal - Yes
sahkan-bitshares - Yes
xn-delegate - Yes
fox - Yes
witness.yao - No
magicwallet.witness - No
blckchnd - Yes
delegate.freedom - No
crazybit - Yes
bangzi - Yes
witnes.hiblockchain - Yes
gdex-witness - No
openledger-dc - No (Because they set OL as proxy for all new users by default)
delegate-zhaomu - Yes
winex.witness - Yes
clockwork - Yes
delegate.ihashfury - Yes
zapata42-witness - Yes
btspp-witness - Yes

Worker Proposals Active
201808-trusty-community-ui-p1 - Yes
201803-bitshares-core - Yes
201803-bsip32 - Yes
201803-bsip30 - Yes
201803-bsip33 - Yes
201803-bsip34 - Yes
201803-bsip35 - Yes
201803-bsip37 - Yes
201803-bsip36 - Yes
201803-bsip31 - Yes
201710-spokesperson - No, due to conflict of interest with DASCoin and her complete absence ever since this proposal was passed.
201802-legal-bts - Yes
201804-bitfest - Yes
201802-documentation - Yes
201804-general-presentation - Yes
201710-compliance - Yes
DEXBot - User Friendly BitShares Market Making Bots ($660/d) - Yes
201803-bsip38 - Yes
201807-infrastructure - Yes
201807-hackthedex - Yes
committee controlled open market operation fund - No, this WP is hogging way too much of the RP and leaving very little for other WPs.
refund100k - Yes
201808-bitshares-ui - Yes, but if I don't see some effective UI changes to the reference wallet within the next 3 months I will not be voting for a renewal until manpower issues can be addressed.
201808-flash-global-infrastructure - Yes

Worker Proposals Proposed
201902-marketing-interviews-articles-and-visibility - Yes
2018-10-decentralized-sponsorship - Yes
Poll - BSIP42 - NO adjustment to price feed - Yes
201810-bitshares-org - Yes
201808-bsip40-1 - Yes
refund400K - No
201807_OpenLedger_Security_Analysis - No because I can't wrap my head around the purpose of this WP.
Android Custom Token Wallet - Yes
The rest are pretty self explanatory.

33
Stakeholder Proposals / [Proxy] kimchi-king - Journal
« on: July 25, 2018, 02:54:47 pm »
I will keep this thread updated to reflect all my voting decisions.

If you wish to have me as your proxy then please enter kimchi-king on the "Voting" page found in your wallet.



Don't forget to save your changes.

34
First off, I would like to thank APAsia.tech, DL, and DAOStreet for everything they have done and are doing for the BitShares community. These guys are top-notch supporters and deserve equal support from the BitShares community.

I've been looking forward to this WP for quite some time and know this will be put to great use. As we can see above, DL is a dedicated professional with extensive networking knowledge which shouldn't be lost due to lack of funding. We have an extensive war chest and it would be a shame if his efforts are destroyed.

I will be voting for this once it goes live.

35
Sounds like a good idea.

Thanks Abit for sharing your thoughts on this WP. I hope that other proxies & committee members follow your lead to come forward and express their support or concerns publicly about this initiative.

36
I very much welcome you engagement as well your offer to be trusted proxy!
We need more people going forward and wanting to take an active role in the community!
So ... +5%!

Thank you Fabian for expressing your support. I really appreciate it.

37
I would like to express my support for this renewal. Thank you for all of your continued efforts to ensure the BitShares network grows and is able to handle the increased network activity.

38
John will be a fantastic addition to the BitShares Committee without out a doubt. He is a man of action which the community always welcomes. I fully support John and hope that others will do the same.

39
Stakeholder Proposals / Re: Smaller Worker Funds
« on: June 27, 2018, 06:01:20 pm »
One way would be to have a general budget worker according to the budget worker model of the BBF. It would need to have some kind of board that decides what is actually being funded.

This is probably the most straightforward and efficient option available. I can suggest to the BitShares Cabinet that we consider supporting this effort since it already falls within our intended purview.

40
Stakeholder Proposals / Re: [Worker] BitFest in Amsterdam
« on: June 21, 2018, 11:37:29 pm »
Voted and I hope I can make it.

41
Hi everyone, my name is Kevin Messerly, but people call me Kimchi-King and I'm a BitShares addict.

Damn it feels good to get that off my chest.

It all started a few years ago when I came across BitShares on coinmarketcap.com. I did some digging and discovered that this was something I could dip my toes in, but it wasn't until early 2017 that I decided to become more involved in the community. Since then, I have spent countless hours answering questions, giving advice, providing support to numerous BitShares based projects, acting as admin in many rooms on Telegram and Discord, and doing my best to promote BitShares on social media. Why? Because I understand that without an active community BitShares will never reach its true potential.

I've finally decided to humbly request for your trust and support so if you're willing I'd be honored to be your proxy.

I promise to remain objective to the principles that BitShares stands for, to keep my supporters informed of my voting choices, and to continue to be an active member of this outstanding community. BitShares has the power to be the worlds most powerful financial tool, but being decentralized has its shortcomings and I will to do my part to bring BitShares to its much deserved place in the crypto space.

If you're willing to add me as your proxy then please use this BitShares address kimchi-king.

For full disclosure, I'm a part of the BitShares cabinet which is made up of the same team behind the DEXBot project. We plan to develop, present, and support numerous worker proposals designed to benefit the BitShares community and ecosystem. We will do this by acting as middle management between companies looking to develop product/services for BitShares and the major stakeholders. This will help to increase the usage of the Reserve Pool funds for the sole purpose of benefiting all BitShares holders.

We understand that not many people or companies have the time to invest in establishing a strong reputation amongst the community to ensure their proposals gain enough traction to get their worker proposals approved. In order to assist those interested in providing/developing products/services for BitShares the Cabinet members will be responsible for conducting due diligence, market research, worker proposal development, product management, development oversight, worker proposal marketing, escrow services, and the list goes on.

If you have any questions please don't hesitate to contact me on Telegram (@kimchiking), Discord (kimchi-king#0714), Twitter (@kevinmesserly), or via email at kimchikingbts@gmail.com

I've created this dedicated Telegram channel to inform the community and my supporters of the decisions I've made, wish to make, and refuse to make with regards to my voting power. Here's the link to the channel. https://t.me/kimchiclub

42
First off, I'm truly grateful for everything that DL and the AP Asia Tech team have done for the BitShares community and network in general.

I would like to express my full support for this initiative and hope that the BBF accepts this offer for collaboration. Decentralization is the cornerstone of BitShares and what is being presented in this thread is one way to ensure that it remains so.

43
Bitspark [closed] / Re: Bitspark Rebrands
« on: April 20, 2018, 08:26:10 am »
Welcome Bitspark to BitShares Talk.

Thanks for sharing this wonderful information.

I'm extremely excited about the future for Bitspark and the Zephyr Project.

Keep up the outstanding work.

44
General Discussion / DEXbot Progress Report for 13 April 2018
« on: April 14, 2018, 05:27:50 pm »
DISCLAIMER: DEXBOT IS NOT A RISK-FREE ENDEAVOR AND ANY TRADING BOT CARRIES SIGNIFICANT RISK. THE DEXBOT TEAM DO NOT GIVE TRADING ADVICE AND RELY ON USERS TO DO THEIR OWN RESEARCH AND EVALUATE THE RISKS BEFORE PARTICIPATING IN THE PROJECT OR USING ANY PRODUCT FUNDED, CREATED, OR MENTIONED BY THE DEXBOT TEAM.

The DEBOT Cabinet: @Permie, @MarkoPaasila, @Kimchiking, Cryptick, Taconator

DEXBOT is an approved BitShares Worker Proposal receiving funding equivalent to $667 per day to build an open-source and simple to use trading bot to help provide liquidity to the DEX.

Liquidity is the life-blood of an exchange and we believe that a widely distributed trading bot will help crowd-source the provision of liquidity.

The DEXBOT team is looking for new developer talent to continue colloborating on this open-source project.

Join the conversation with Telegram in our “DEXBot” channel: https://t.me/DEXBOTbts

Visit www.dexbot.info

Here's our progress since the last report;

DEXBOT IS NOW AVAILABLE FOR ALL TO INSTALL ON LINUX!

There are still bugs, and DEXBOT is by no means a finished product but it is ready for user testing. If you're handy with linux you should be able to get it running to play around with.
“Relative orders” strategy only right now. “Staggered Orders” will be added at a later date. Relative orders is a difficult strategy to implement without a bot so it is the priority. DEXBOT can place both a buy and a sell order for a defined % above/below the current market price. Just as “btsbots” did previously, but with a more “user friendly” (hopefully!) interface.

- Windows OS DEXBOT is upcoming for release in the next few weeks. The development company “Codaone” (the lead dev-team) are close to a Windows release.

- The DEXBOT cabinet have decided to change from paying per milestone, and instead begin paying per feature; payment at successful delivery of a new release with one or more new features and critical bugs fixed. Codaone are happy with this arrangement.

- The DEXBOT channel: https://t.me/DEXBOTbts has 10-15 active volunteers playing with DEXBOT installation on linux (and one guy braving the buggy and incomplete Windows installation with little success ha!).

- Bug reports are being submitted to Github. Bug-fixes and new releases are coming regularly as the Codaone team respond to issues found by these volunteers.

- If you want to join in and be one of the very first people to run DEXBOT on a “relative orders” strategy come and introduce yourself and get help setting yourself up. The more people testing the software the faster DEXBOT can reach a stable release.
https://github.com/codaone/DEXbot

- DEXBOT is open-source and the team are already aware of at least one user forking the software to create a cross-exchange arbitrage bot; allowing the prices on the DEX to better mirror the price action on Binance and other Centralized Exchanges (CEX's). We want to see more people do the same; fork DEXBOT and add to the value of the BTS DEX. The Reserve Pool's funding of DEXBOT creates a framework/foundation product that demonstrates to the market what the DEX is capable of. The free market of individuals will (and is right now!) swarm around the core-dexbot development and spawn new ideas from it.

- Public polls will be taken in the near future, perhaps on a 2-weekly basis, to get input from the community of DEXBOT users on which features/updates/bug fixes are deemed most important. By taking input from the people who actually use DEXBOT the DEXBOT-cabinet aim to direct development progress as efficiently as possible.

- JT, the CryptoBridge Community Manager, and the CryptoBridge Team have been invited into public discussions to so as to better inform them of DEXBOT progress and demonstrate that DEXBOT can be forked by them to better suit their customers. For example CryptoBridge could work to remove the “bridge.” prefix from assets traded on their exchange so as not to confuse their customers. This is all in aid of increasing the liquidity available on the DEX. Any exchange with a BTS order-book is welcome to join the discussion and approach the DEXBOT Cabinet for information.

- Most development effort recently has been spent squashing bugs and making the bot behave as a user would naturally expect. Closed issues can be seen here: https://github.com/codaone/DEXbot/issues?q=is%3Aissue+is%3Aclosed

- Individual bots within a BTS account using DEXBOT are called “workers”. Multiple “workers” (up to 10) are now supported in the GUI. This was included in Milestone 3. Commits to this release can be seen here: https://github.com/codaone/DEXbot/commits/0.1.5

Money spent:
- Development Work for Milestone 3 $5880 to Codaone

- Project Management during Milestone 2 – 15hours - $1050 – Codaone

- Project Management during Milestone 2 – 15hours - $450 – Markopaasila

- UX Design Work during Milestone 3 - $140 – Codaone (Not implemented yet as not high priority)

- For a total and complete view of transactions please view the BTS account
“dexbot-worker-escrow”

What's next
- The DEXBOT cabinet aim to provide a fully functioning&stable DEXBOT, with bug fixes and updates via the Codaone team.

- Once a suitably stable bot has been built, the cabinet aim to approach BTS-powered exchanges such as OpenLedger, CryptoBridge, Rudex etc and introduce them to DEXBOT and it's uses to increase liquidity on their exchanges.

- Create content for the www.dexbot.info website such as videos, instructional guides, performance reporting.
Continue to increase and maximise the liquidity brought to the DEX via DEXBOT.

How & What you can do to contribute:
- If you are a dev or know one, now is the time to join! We will pay bounties for project-work-completed. This is likely to be paid in arrears. Join the community and get to work and if you produce something of value the team want to pay you for it. One must understand that the DEXBOT team has budget limitations and a defined scope of work but that we want to incentivize BTS-related development work relevant to DEXBOT as far as possible.

- Training to work with the BitShares codebase will also give you the opportunity to build a reputation for yourself and set yourself in good stead to get involved in future projects too.

- If you have an opinion about market making strategies please contribute to the definitions of strategies

- Any other talents, like graphics, data analysis, scripting, content creation, animations; join the chat and figure out how to get your efforts recognized. We are willing to pay for every valuable contribution.

- Join the Market Makers Community and learn how to do it profitably. MARKET MAKING IS A RISK-ON ACTIVITY. Nothing is guaranteed and one trades at their own risk.

45
General Discussion / DEXBOT Progress Report for 24th February 2018
« on: February 24, 2018, 05:17:31 pm »
Team Members: @Permie, @MarkoPaasila, @Kimchiking, Cryptik, Taconator

DISCLAIMER: DEXBOT IS NOT A RISK-FREE ENDEAVOUR AND ANY TRADING BOT CARRIES SIGNIFICANT RISK. THE DEXBOT TEAM DO NOT GIVE TRADING ADVICE AND RELY ON USERS TO DO THEIR OWN RESEARCH AND EVALUATE THE RISKS BEFORE PARTICIPATING IN THE PROJECT OR USING ANY PRODUCT FUNDED, CREATED, OR MENTIONED BY THE DEXBOT TEAM.

DEXBOT is an approved BitShares Worker Proposal receiving funding equivalent to $667 per day to build an open-source and simple to use trading bot to help provide liquidity to the DEX.

Liquidity is the life-blood of an exchange and we believe that a widely distributed trading bot will help crowd-source the provision of liquidity.

The DEXBOT team is looking for new developer talent.

Join the conversation with Telegram in our “DEXBot Project Chat” channel: https://t.me/BTSLiquidityBotWorkerProposal

Here's our progress so far:

• The initial alpha-version of the bot with a Graphical User Interface has been completed which includes a strategy to provide a sell and buy wall at defined spread and price.

• Ian Haywood has contributed with an interactive cli mode for setting up a similar strategy, but which attempts to follow market price dynamically.

• Gabriel has worked on a website for providing information and guides. http://dexbot.tk

• A logo has been designed.

• The github repo is open for contributions, issues and discussions.

• The escrow account multisig parties have agreed on how to agree on payments and cultivate participation and collaboration for maximal value.

• Although the WP was approved slowly, we are almost on track with the original roadmap.

• It turned out to be not-so-straightforward to compile the software into a Windows package. We chose not to let this stop progress on features, and it will be solved at a later point.

• A line of communication was established between the DEXBot project and Autonio to avoid duplication of efforts and allow for possible synergies.

• A market makers community is being born in anticipation of a bot to boost efforts. People are learning the basics there and already providing additional liquidity.

• Taconator was chosen to be included in the multisig to replace cryptokong. The DEXBOT team gave 1 weeks notice for any BTS community members to voice complaint. This notice period expired yesterday and Taconator will be added to the multi-sig WP account today. The required threshold to approve transactions will be increased from 3 of 4 to 4 of 5.

Money spent:

• Nothing. One weeks payment worth of BitUSD ($4620) bought off the market. The development team Codaone who have accepted (a portion of) the WP contract understand that payment will be approved once they reach pre-defined milestones.

What's next:

• Bugfixes

• The "Relative Orders" strategy will be able to follow market price dynamically, which will make it suitable for all markets. This will include one or more possible methods.

• Features will be added which help keep the strategy balanced, so the account doesn't run out of the other asset.

• The github repo will be populated with feature requests to be prioritized by the escrow-multisig participants.

• Attempts to make an executable file to easily install the bot without comand-line knowledge will be continued.
Developers with experience packaging .exe files are needed! Apply within; https://t.me/BTSLiquidityBotWorkerProposal

• The GUI and CLI interfaces will be worked on to support the same features and strategies.

• Add the possibility of editing a bot after creation.

• Continued efforts to streamline collaboration, increase ROI, include new contributors.

• Improve the website with documentation.

How & What you can do to contribute:

• If you are a dev or know one, now is the time to join! We will pay bounties for pre-defined milestones. Training to work with the BitShares codebase will also give you the opportunity to build a reputation for yourself and set yourself to get involved in future projects too.

• If you have an opinion about market making strategies please contribute to the definitions of strategies.

• Any other talents, like graphics, data analysis, scripting, content creation, animations; join the chat and figure out how to get your efforts recognized. We are willing to pay for every valuable contribution.

• Join the Market Makers Community and learn how to do it profitably.

Pages: 1 2 [3] 4