last time he was simply not interested, was not a matter of offering more $. maybe that changed now, not sure.

Why don't we just offer his more $$ then? Have him submit proposal for a rate that would bring him over immediately?

vikram was with us until the workers were suspended due to high price in bitshares. we asked vikram to submit a new worker in bitusd but he was moving on into working in a new chain project outside bitshares. of course this was a big loss, i am trying with my reduced skills compared to him to do the basic maintenance he was doing since then.

It would be a terrible shame to lose Vikram.

Why did this worker never get approved? Was the proposal flawed in some way?

Thanks for the support guys. Things are a bit hectic for me at the moment, but once I get a few things out of the way, I will likely look into some sort of limited worker using an arrangement similar to what was mentioned earlier.

@vikram is great, will be of big value for us if we can have any way to keep him involved. the best of the luck with your project also vikram!

Quote from: bang-king on June 17, 2017, 12:57:54 AM

Quote from: vikram on June 15, 2017, 12:27:46 AM

Unless this worker gets voted back in at some point, all of my focus is now dedicated to the upcoming Soledger blockchain project. I will make an initial announcement on the project after development has progressed a bit more. The details may change, but my hope is that the project can directly benefit the members of the BitShares community. If possible, I hope to also give an extra bonus to those who directly supported myself and Soledger either through this worker, or with other contributions to the project in the future.

create a new worker proposal in bitusd like @xeroc.  your current worker is too expensive at this point.

@vikram This is a good idea, any interest in doing so?  With the BTS and crypto market heating up, continued development would be a great asset.  Even if you can only do it part time etc...

@vikram thanks for your work. We do like you to be around, however, the pay of current workers are a bit too high according to current market price/rate of BTS token (around $3k per day). As quoted below, if you still like to be paid to work with this project, please consider creating a new worker proposal like @xeroc's -- multisig and be paid in bitUSD. Related link: https://bitsharestalk.org/index.php/topic,23770.0.html

Quote from: bang-king on June 17, 2017, 12:57:54 AM

Quote from: vikram on June 15, 2017, 12:27:46 AM

Unless this worker gets voted back in at some point, all of my focus is now dedicated to the upcoming Soledger blockchain project. I will make an initial announcement on the project after development has progressed a bit more. The details may change, but my hope is that the project can directly benefit the members of the BitShares community. If possible, I hope to also give an extra bonus to those who directly supported myself and Soledger either through this worker, or with other contributions to the project in the future.

create a new worker proposal in bitusd like @xeroc.  your current worker is too expensive at this point.

Quote from: vikram on June 15, 2017, 12:27:46 AM

Unless this worker gets voted back in at some point, all of my focus is now dedicated to the upcoming Soledger blockchain project. I will make an initial announcement on the project after development has progressed a bit more. The details may change, but my hope is that the project can directly benefit the members of the BitShares community. If possible, I hope to also give an extra bonus to those who directly supported myself and Soledger either through this worker, or with other contributions to the project in the future.

create a new worker proposal in bitusd like @xeroc.  your current worker is too expensive at this point.

Thanks for your work, Vikram!

A few updates:

• Merged broadcast_transaction_synchronous API addition from Steem by @ElMato (https://github.com/bitshares/bitshares-core/pull/311)
• Merged get_asset_holders API fix from @oxarbitrage  (https://github.com/bitshares/bitshares-core/pull/312)
• Merged Windows build fix from @abit (https://github.com/bitshares/bitshares-core/pull/299)
• Documented OpenSSL compatibility issue (https://github.com/bitshares/bitshares-core/wiki)
• Merged minor graphene constant cleanups from @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/309, https://github.com/bitshares/bitshares-core/pull/310)
  
• Added additional seed node from @sahkan (https://github.com/bitshares/bitshares-core/pull/286)
• Merged Visual Studio compatibility fix from btsabc for bitshares-fc (https://github.com/bitshares/bitshares-fc/pull/4)
• Miscellaneous bitshares-fc cleanup (https://github.com/bitshares/bitshares-fc/commits/master)

Huge thanks to everyone who supported this worker. One of the unique things about BitShares is how decentralized its development is, and over time I've added active contributors directly to the BitShares GitHub organization. I think this plays an important part in helping ensure that BitShares will continue to improve and grow, without needing to depend on any single person. Special thanks to @abit, @ElMato, @oxarbitrage, @pc, @svk, @xeroc and any other team members for their continuing work.

Unless this worker gets voted back in at some point, all of my focus is now dedicated to the upcoming Soledger blockchain project. I will make an initial announcement on the project after development has progressed a bit more. The details may change, but my hope is that the project can directly benefit the members of the BitShares community. If possible, I hope to also give an extra bonus to those who directly supported myself and Soledger either through this worker, or with other contributions to the project in the future.

As always, anyone still feel free to contact me about helping organize things on the GitHub or forum, or other related issues to help the improve the community.

Thanks.
More docs need to update.

• Fixes to re-indexing decisions and behaviour (https://github.com/bitshares/bitshares-core/commit/f13698370b9eb2d64677bad0e2bc6a52aa93f039)
• Merged upstream JSON RPC improvements (https://github.com/steemit/fc/issues/13)
• Updated seed nodes (https://github.com/bitshares/bitshares-core/compare/8c0668de367b3826c52e4217880eb8a227caadf7...cda895abd6d7a7d4556d63e31f61438f310ead9f)
• Fixed broken reference links and cleaned out old pages on GitHub wiki (https://github.com/bitshares/bitshares-core/wiki)
• Cleaned up bitshares-core GitHub branches

I am looking forward to see whether the upcoming Peerplays blockchain might have any general Graphene patches that could be applicable to BitShares.

• Merged memory leak fix by @abit (https://github.com/bitshares/bitshares-core/pull/257)


• Merged -track-account command line argument fix by @abit (https://github.com/bitshares/bitshares-core/pull/259)


• Merged get_full_accounts API enhancement by @alt (https://github.com/bitshares/bitshares-core/pull/261)


• Merged console P2P error issue fix by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/264)


• Merged new get_block_header_batch API by @oxarbitrage (https://github.com/bitshares/bitshares-core/pull/263)


• Fixed compilation compatibility with new Clang 4.0.0 (https://github.com/bitshares/bitshares-fc/commit/908762d687eccab019403189fd1d95502fb75c89#commitcomment-21919423)