I know hashcows pays out in SC, but we need something like blackCoin.
A pool that only pays out in Silk. Hashcows works a little bit difficult
With the low prices atm and small walls we can bring it up very easily.
Topic: [ANN][SILKCOIN][DARKSILK PREANN][TESTING STORMNODES/DarkSIlk MARKET/I2P] - page 200. (Read 289509 times)
July 07, 2014, 12:21:38 PM
July 07, 2014, 12:08:57 PM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
it's pos, not pow
I know, but you can setup a multipool.
So you are mining another coin, sell that coin and with the btc you buy Silkcoin
!Yes this would be awesome. Have talked to a couple miners but so far no headway for multipool. If you or anyone trustworthy (key) that you know can setup a multipool that would be amazing.
Key thing is trustworthy pool management with regular and timely payments for miners.
If anyone has any plans for a multipool please join us on gchat. It will be an essential tool for the success of Silk(coin) haha [email protected]
You can setup to be paid in SC in this multipool already.
https://hashco.ws/
July 07, 2014, 11:57:55 AM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
it's pos, not pow
I know, but you can setup a multipool.
So you are mining another coin, sell that coin and with the btc you buy Silkcoin
!Yes this would be awesome. Have talked to a couple miners but so far no headway for multipool. If you or anyone trustworthy (key) that you know can setup a multipool that would be amazing.
Key thing is trustworthy pool management with regular and timely payments for miners.
If anyone has any plans for a multipool please join us on gchat. It will be an essential tool for the success of Silk(coin) haha [email protected]
July 07, 2014, 11:15:16 AM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
it's pos, not pow
I know, but you can setup a multipool.
So you are mining another coin, sell that coin and with the btc you buy Silkcoin
!mhmh ok! good idea
July 07, 2014, 11:10:15 AM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
it's pos, not pow
I know, but you can setup a multipool.
So you are mining another coin, sell that coin and with the btc you buy Silkcoin
! July 07, 2014, 11:07:25 AM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
it's pos, not pow
July 07, 2014, 11:02:18 AM
Is it possible to setup a Silkcoin pool?
On this way we can get things a little bit moving on the exchanges...
On this way we can get things a little bit moving on the exchanges...
July 07, 2014, 10:43:26 AM
Cool
Thanks Arteleis
Price is getting up
Thanks Arteleis
Price is getting up
July 07, 2014, 10:01:40 AM
Thank you guys! I can see my coin again with the 1.0.9.3 wallet update!Having the wallet fixed looks like the least of the work being done around here.
I love the idea of voting for features as a community in wallet! This line of thinking makes Silkcoin a valuable currency indeed.
I was wondering, will you need to own any coin to vote?
Thank you again!
Yes, voting will be paid and all funds will go directly to development from the voting process. We are working on a combination of paid vote, diminished paid vote, confirmations, and voter ranking system to make the voting process as secure and fair as possible.
I'm not going to give too many details quite yet, but i can say the backend is finished.. and project is aimed to be released this week so we can all finalise the name/rebranding dispute and move forward with marketing/fundraising and further decisions as a community.
As we presently have clear options for the first poll(s) there will not need to be community proposals from the polling site as the proposals have of course been raised in the forum.
But for future proposals (perhaps after a couple votes) for polls a ranking system will be used to raise proposals and rally signatures for a concern to be properly voiced and a poll raised.
So it will be necessary once poll is up to be active (even be it 1 silk - 1 silk per vote) in order to recieve your poll rankings and raise future proposals.
Once site is up we will definitely be open to review and scrutiny regarding the security and fairness of the system and will regularily update the system if any weakness is found.
July 07, 2014, 09:04:42 AM
Ill try and give trello a bit of a tidy up tomorrow, ive been busy with work this week, but will try and get round to it.
I will refine the final logo artwork and upload some high res vector images in SVG format that the devs can work with and incorporate into the wallet.
Keep up the good work guys, remember that we need to come back better and stronger than before, and im confident that we will!
Over and out for me on this side of the earth, see you in the morning!
I will refine the final logo artwork and upload some high res vector images in SVG format that the devs can work with and incorporate into the wallet.
Keep up the good work guys, remember that we need to come back better and stronger than before, and im confident that we will!
Over and out for me on this side of the earth, see you in the morning!
Roger
July 07, 2014, 07:08:50 AM
Time to buy again
July 07, 2014, 06:54:01 AM
Thank you guys! I can see my coin again with the 1.0.9.3 wallet update!Having the wallet fixed looks like the least of the work being done around here.
I love the idea of voting for features as a community in wallet! This line of thinking makes Silkcoin a valuable currency indeed.
I was wondering, will you need to own any coin to vote?
Thank you again!
July 07, 2014, 06:13:22 AM
Ill try and give trello a bit of a tidy up tomorrow, ive been busy with work this week, but will try and get round to it.
I will refine the final logo artwork and upload some high res vector images in SVG format that the devs can work with and incorporate into the wallet.
Keep up the good work guys, remember that we need to come back better and stronger than before, and im confident that we will!
Over and out for me on this side of the earth, see you in the morning!
I will refine the final logo artwork and upload some high res vector images in SVG format that the devs can work with and incorporate into the wallet.
Keep up the good work guys, remember that we need to come back better and stronger than before, and im confident that we will!
Over and out for me on this side of the earth, see you in the morning!
July 07, 2014, 02:48:42 AM
I added a note on the Trello board about possible improvements regarding the development. I also post the note here for discussion.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
I believe this is exactly what we're aiming for. Presently Detroit and Bishop are working off each others gits and when finish will be pulled to public repo with all the commits and info you mention.
I am new to github, but am the only one who can write to present public repo. It was suggested like this for security purposes as you mention.
In saying this, the location of the public repo may or may not change. It is of course optimal to have 2 skilled, trusted coders to review and accept commits.
My github can be used for this as long as it is in the interest of security and commitment to the community.
We will be of course looking for more coders to conduct peer review of the forks and test branches.
Feel free to add me on gchat if you want to talk more, as well as any coders willing to do peer review.
[email protected]
Also, I'd like to clarify that I consider the trello board excellent for organization and planning and that the work that has been done so far is fantastic. All the above suggestions for using github are for all tasks related to coding.
Yep trello is awesome although its prob due for a.little tidying. Lotsss of info in there. Posted the repo code in regards to the github process. Standard protocol, which i think is the same as youve mentioned. If we missed something or theres a problem you noticed let me know.
July 07, 2014, 02:16:00 AM
I added a note on the Trello board about possible improvements regarding the development. I also post the note here for discussion.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
Just a bit if further explanation as noted at the bottom of the present repo.
Code:
Development process
Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.
The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.
The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Silkcoin.
Feature branches are created when there are major new features being worked on by several people.
From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.
Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.
July 07, 2014, 01:51:31 AM
Hanz, check your PM's: further-refined ANN inside with new exchange + social graphics; tightened layout.
More advanced modules to come tomorrow
Ben
More advanced modules to come tomorrow
Ben
ANN updated. Nice work Ben!
July 07, 2014, 01:50:50 AM
Any idea when the new client will be ready?
Guys we need to have regular updates from the devs posted here so that investors checking out our thread know progress is being made.
It will also help reduce FUD.
Guys we need to have regular updates from the devs posted here so that investors checking out our thread know progress is being made.
It will also help reduce FUD.
New stable client with many fixes is at the top of the ANN. 1.0.9.3
Notes of fixes at the top of the ANN.
1.0.9.4 being worked on hard by Bishop and Detroit.
Original code (1.0.9.2 and older) is in rough shape, and is taking extensive time and effort to clean up.
We'd like to release 1.0.9.4 this week and is currently is testing phases. I will update as we are closer to finalizing a release date.
Otherwise, the network is sound and the 1.0.9.3 wallet is working correctly with the exception of some market data issues (of course being worked on for next upgrade.)
All is well.
Awesome. Thanks a lot for this man.
You're doing an awesome job with this thread
Thank you! Let me know what i can do to make this community better and ill do it. (-;
July 07, 2014, 01:48:02 AM
I added a note on the Trello board about possible improvements regarding the development. I also post the note here for discussion.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
I'd suggest that, once the coin name is determined (changed or not):
1) a Github Organization should be setup and should be joined by those dev team members that should have write access to the source code repository. Everybody can contribute by creating pull requests, but only a few should have write access to the repo for security.
2) The github issue tracker should be fully utilized as far as coding is involved (bugs, tasks, etc etc). This would help with transparency and organization as we would all know which task is assigned to whom and what the progress is.
3) Commits should be pushed to the public repository (branches could be utilized for feature testing etc), unless there are security reasons not to do so.
4) Everybody should feel free to post feedback or open issues at the github issue tracker.
5) Perhaps the wiki feature of github should also be used for technical documentation.
Trello is good for many things but not for organizing a software project. These are just some ideas. Feel free to comment on them.
I believe this is exactly what we're aiming for. Presently Detroit and Bishop are working off each others gits and when finish will be pulled to public repo with all the commits and info you mention.
I am new to github, but am the only one who can write to present public repo. It was suggested like this for security purposes as you mention.
In saying this, the location of the public repo may or may not change. It is of course optimal to have 2 skilled, trusted coders to review and accept commits.
My github can be used for this as long as it is in the interest of security and commitment to the community.
We will be of course looking for more coders to conduct peer review of the forks and test branches.
Feel free to add me on gchat if you want to talk more, as well as any coders willing to do peer review.
[email protected]
July 07, 2014, 01:01:35 AM
Any idea when the new client will be ready?
Guys we need to have regular updates from the devs posted here so that investors checking out our thread know progress is being made.
It will also help reduce FUD.
Guys we need to have regular updates from the devs posted here so that investors checking out our thread know progress is being made.
It will also help reduce FUD.
New stable client with many fixes is at the top of the ANN. 1.0.9.3
Notes of fixes at the top of the ANN.
1.0.9.4 being worked on hard by Bishop and Detroit.
Original code (1.0.9.2 and older) is in rough shape, and is taking extensive time and effort to clean up.
We'd like to release 1.0.9.4 this week and is currently is testing phases. I will update as we are closer to finalizing a release date.
Otherwise, the network is sound and the 1.0.9.3 wallet is working correctly with the exception of some market data issues (of course being worked on for next upgrade.)
All is well.
Awesome. Thanks a lot for this man.
You're doing an awesome job with this thread
July 06, 2014, 11:57:33 PM
Hanz, check your PM's: further-refined ANN inside with new exchange + social graphics; tightened layout.
More advanced modules to come tomorrow
Ben
More advanced modules to come tomorrow
Ben
Jump to: