Topic: [ANN] SLING | Fully Working DECENTRALIZED MARKET in Wallet | SLING MARKET LIVE - page 4. (Read 178758 times)
September 30, 2015, 09:36:26 PM
There is a Sling de-list warning on Bittrex again.
September 22, 2015, 06:44:43 PM
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
True. 7 SLING for a listings?Sounds good, the question is what to do with that fee's, burn it to increase the Value of Sling or for a develop fund or give it back to MN Operator or a mix of all.
What about something like;
50% Back to MN Op
30% Dev Fund
20% Burned
Just a thought
i like it, would increase the Revenue for MN Operator dramatically, could lead to a new wave of MN...
listings will cost 7 SLING with the fee breakdown below:
50% Masternodes
30% Dev Fund
20% Burned
I am thinking about forking I/O-Coin for user name registration (https://github.com/IOCoin/iocoin).
How many Sling to purchase a user name or what breakdown 5 Sling, 10 Sling, 15 Sling, 25 Sling, 37 Sling, 50 Sling ? User names are needed for the reputation/rating system.
I am also working on refreshing the core libs that support masternodes with Dash's v0.12.0.53 (released 18 days ago). After that SLING will support InstantX and MN Consensus Voting.
Update: I/O Coin uses a central server for user name registration, NOT a blockchain so we can't use it.
September 22, 2015, 01:54:39 PM
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
True. 7 SLING for a listings?Sounds good, the question is what to do with that fee's, burn it to increase the Value of Sling or for a develop fund or give it back to MN Operator or a mix of all.
What about something like;
50% Back to MN Op
30% Dev Fund
20% Burned
Just a thought
i like it, would increase the Revenue for MN Operator dramatically, could lead to a new wave of MN...
September 22, 2015, 06:48:04 AM
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
True. 7 SLING for a listings?Sounds good, the question is what to do with that fee's, burn it to increase the Value of Sling or for a develop fund or give it back to MN Operator or a mix of all.
What about something like;
50% Back to MN Op
30% Dev Fund
20% Burned
Just a thought
September 22, 2015, 03:36:22 AM
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
True. 7 SLING for a listings?Sounds good, the question is what to do with that fee's, burn it to increase the Value of Sling or for a develop fund or give it back to MN Operator or a mix of all.
September 22, 2015, 01:32:32 AM
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
True. 7 SLING for a listings? September 22, 2015, 01:13:34 AM
I would clearly vote AGAINST such a Process, if both Party's need to run the Node, that is simply not convienent enough. Let's think about
storing that Information crypted in the MN(s)? If you enter an Item in the Marketplace for like 7 Days Duration, the MN(s) will store this Information for the next 7 Days.
storing that Information crypted in the MN(s)? If you enter an Item in the Marketplace for like 7 Days Duration, the MN(s) will store this Information for the next 7 Days.
Great points and I agree except for a one time category fee. I think the category fee should be renewed and auctioned to the highest bidder but this is way more dev.
The messaging is a BIG problem and this is the same for all coins with secure messaging (Shadow, etc...). Using Masternodes as temp cache for the encrypted messages is a good idea. Storing pieces or shards of the crypt on masternodes (like Storj) but again this is way more dev.
I think Fee's are important to:
a) Reduce the Spam and Noise in the Marketplace
b) could be used to enrich the MN Payout's or to send x% to a Development Fund similar to what Dash is doing.
c) creating Category's could also be restricted via a big one time Fee, like 2500 Sling for a new Category. ( with something like contracts in ETH the Creator of the Category could get back with each Item which is placed in his Category X Sling.
a) Reduce the Spam and Noise in the Marketplace
b) could be used to enrich the MN Payout's or to send x% to a Development Fund similar to what Dash is doing.
c) creating Category's could also be restricted via a big one time Fee, like 2500 Sling for a new Category. ( with something like contracts in ETH the Creator of the Category could get back with each Item which is placed in his Category X Sling.
Is anyone opposed to a required market listing fees?
How much should Sling listing fees cost: 1 SLING, 2 SLING, 3 SLING, 5 SLING, 7 SLING or 10 SLING?
1 Sling would not prevent anyone from spamming. My first thought was 5-10 Sling.
September 21, 2015, 06:00:22 PM
I would clearly vote AGAINST such a Process, if both Party's need to run the Node, that is simply not convienent enough. Let's think about
storing that Information crypted in the MN(s)? If you enter an Item in the Marketplace for like 7 Days Duration, the MN(s) will store this Information for the next 7 Days.
storing that Information crypted in the MN(s)? If you enter an Item in the Marketplace for like 7 Days Duration, the MN(s) will store this Information for the next 7 Days.
Great points and I agree except for a one time category fee. I think the category fee should be renewed and auctioned to the highest bidder but this is way more dev.
The messaging is a BIG problem and this is the same for all coins with secure messaging (Shadow, etc...). Using Masternodes as temp cache for the encrypted messages is a good idea. Storing pieces or shards of the crypt on masternodes (like Storj) but again this is way more dev.
I think Fee's are important to:
a) Reduce the Spam and Noise in the Marketplace
b) could be used to enrich the MN Payout's or to send x% to a Development Fund similar to what Dash is doing.
c) creating Category's could also be restricted via a big one time Fee, like 2500 Sling for a new Category. ( with something like contracts in ETH the Creator of the Category could get back with each Item which is placed in his Category X Sling.
a) Reduce the Spam and Noise in the Marketplace
b) could be used to enrich the MN Payout's or to send x% to a Development Fund similar to what Dash is doing.
c) creating Category's could also be restricted via a big one time Fee, like 2500 Sling for a new Category. ( with something like contracts in ETH the Creator of the Category could get back with each Item which is placed in his Category X Sling.
Is anyone opposed to a required market listing fees?
How much should Sling listing fees cost: 1 SLING, 2 SLING, 3 SLING, 5 SLING, 7 SLING or 10 SLING?
September 21, 2015, 02:54:09 AM
What exactly does "marketsendshipping"? Does that mean the Buyer provided Shipping Address and is awaiting shipping?
Yes, shipping address to the seller should be part of the buying process. Only problem is the current message delivery relies on both nodes being active. The encrypted message does not persist anywhere (which is good) but that limits the chances of a successful delivery. i think a really important function will be the Reputation. If i'm uncertain on e**y if a Seller is trustwoth or not, i usally screen his Reputation and make my Buy Decision on that.
Reputation is on my list after the new market UI. Vendors and buyers will need user names for the reputation system. Do you think it should be free or Sling should charge per name? Charging helps prevent name spam and makes the masternodes more valuable. How many Sling if we decide to charge for names? This data will need to go on a separate blockchain.Also, should there be a fee to list an item in the market? Again, this prevents spam listings but might turn away vendors.
I would clearly vote AGAINST such a Process, if both Party's need to run the Node, that is simply not convienent enough. Let's think about
storing that Information crypted in the MN(s)? If you enter an Item in the Marketplace for like 7 Days Duration, the MN(s) will store this Information for the next 7 Days.
I think Fee's are important to:
a) Reduce the Spam and Noise in the Marketplace
b) could be used to enrich the MN Payout's or to send x% to a Development Fund similar to what Dash is doing.
c) creating Category's could also be restricted via a big one time Fee, like 2500 Sling for a new Category. ( with something like contracts in ETH the Creator of the Category could get back with each Item which is placed in his Category X Sling.
September 20, 2015, 05:59:07 PM
What exactly does "marketsendshipping"? Does that mean the Buyer provided Shipping Address and is awaiting shipping?
Yes, shipping address to the seller should be part of the buying process. Only problem is the current message delivery relies on both nodes being active. The encrypted message does not persist anywhere (which is good) but that limits the chances of a successful delivery. i think a really important function will be the Reputation. If i'm uncertain on e**y if a Seller is trustwoth or not, i usally screen his Reputation and make my Buy Decision on that.
Reputation is on my list after the new market UI. Vendors and buyers will need user names for the reputation system. Do you think it should be free or Sling should charge per name? Charging helps prevent name spam and makes the masternodes more valuable. How many Sling if we decide to charge for names? This data will need to go on a separate blockchain.Also, should there be a fee to list an item in the market? Again, this prevents spam listings but might turn away vendors.
September 20, 2015, 02:54:56 PM
I'm adding checkpoints to Sling and in the process of testing. The code is in the repo.
The current market buy workflow to buy is a bit chatty and don't think this will work when people really use it.
Current:
Buyer: marketbuy
Seller: marketapprovebuy
Buyer: marketescrowlock
Seller: marketrequestpayment
Buyer: marketreleaseescrow
New/Proposed:
Buyer: marketbuy
Buyer: marketescrowlock
Buyer: marketsendshipping (yes that's a new one I did't code yet)
Seller: marketrequestpayment or marketrefund
Buyer: marketreleaseescrow or marketrequestrefund
I could see using the chatty one for some special transactions where the seller wants to screen buyers but most of the time it will be too tedious and sellers will not use market as it is.
The current market buy workflow to buy is a bit chatty and don't think this will work when people really use it.
Current:
Buyer: marketbuy
Seller: marketapprovebuy
Buyer: marketescrowlock
Seller: marketrequestpayment
Buyer: marketreleaseescrow
New/Proposed:
Buyer: marketbuy
Buyer: marketescrowlock
Buyer: marketsendshipping (yes that's a new one I did't code yet)
Seller: marketrequestpayment or marketrefund
Buyer: marketreleaseescrow or marketrequestrefund
I could see using the chatty one for some special transactions where the seller wants to screen buyers but most of the time it will be too tedious and sellers will not use market as it is.
What exactly does "marketsendshipping"? Does that mean the Buyer provided Shipping Address and is awaiting shipping?
i think a really important function will be the Reputation. If i'm uncertain on e**y if a Seller is trustwoth or not, i usally screen his Reputation and make my Buy Decision on that.
September 20, 2015, 12:51:53 PM
I'm adding checkpoints to Sling and in the process of testing. The code is in the repo.
The current market buy workflow to buy is a bit chatty and don't think this will work when people really use it.
Current:
Buyer: marketbuy
Seller: marketapprovebuy
Buyer: marketescrowlock
Seller: marketrequestpayment
Buyer: marketreleaseescrow
New/Proposed:
Buyer: marketbuy
Buyer: marketescrowlock
Buyer: marketsendshipping (yes that's a new one I did't code yet)
Seller: marketrequestpayment or marketrefund
Buyer: marketreleaseescrow or marketrequestrefund
I could see using the chatty one for some special transactions where the seller wants to screen buyers but most of the time it will be too tedious and sellers will not use market as it is.
The current market buy workflow to buy is a bit chatty and don't think this will work when people really use it.
Current:
Buyer: marketbuy
Seller: marketapprovebuy
Buyer: marketescrowlock
Seller: marketrequestpayment
Buyer: marketreleaseescrow
New/Proposed:
Buyer: marketbuy
Buyer: marketescrowlock
Buyer: marketsendshipping (yes that's a new one I did't code yet)
Seller: marketrequestpayment or marketrefund
Buyer: marketreleaseescrow or marketrequestrefund
I could see using the chatty one for some special transactions where the seller wants to screen buyers but most of the time it will be too tedious and sellers will not use market as it is.
September 19, 2015, 02:41:29 PM
Quote
Thanks. This is fun for me because I am a dork.
You have done a GREAT job!! Keep it coming!
It's hard for the HERO of the coin to be a dork!!! Recent activity on Bittrex is saying something different!!! My book says you're the HERO! I wish I had bought more sub 5K!!! My mistake.
I just managed to get 2.0.0.1 compiled on one of my hosted VPS's
"version" : "v2.0.0.1-g32a928e HTML5 UI",
"protocolversion" : 61337,
"walletversion" : 60000,
"balance" : 7360.41399989,
"newmint" : 0.00000000,
"stake" : 8.91333330,
"blocks" : 148108,
"timeoffset" : 9,
"moneysupply" : 919204.90400000,
"connections" : 8,
Had to use the work-around I used for 1.3.3.7 and 1.3.7.7 ....
sudo nano makefile.unix
remmed #DEFS += -DUSE_SECP256K1
mkdir obj
sudo cp crypto obj/crypto -rR
sudo make -f makefile.unix USE_UPNP=1
sudo strip slingd
Since I already had make install on SECP256K1, I figured it was OK
cd ~/slingDJ/secp256k1
sudo ./autogen.sh
sudo ./configure
sudo make
sudo make install
sudo cp /usr/local/lib/libsecp256k1.* /usr/lib
Haven't gotten to setting up the in-house VMS yet but will test at least 1 more daemon compile on Ubuntu 14.04 and the Windows wallet as soon as I get pfSense working with the new IP block.
September 18, 2015, 07:40:39 PM
WOW, great work CryptoVote!!
So good to see Sling being developed still.
Version is running without Problems so far. Nice Job again. I will monitor if there are Problems with this Version on my End.
Thanks for testing the Windows version. Testing is so important.Slingd 2.0.0.1 would not compile on Linux because of new code in rpcmarket.cpp. I updated the repo again and fixed this issue. I appreciate the folks that brought this issue to my attention.
September 18, 2015, 05:14:47 PM
New Sling Wallet v2.0.0.1 compiled binaries released for Windows: It can be donwloaded here: https://github.com/CryptoDJ/sling/releases/tag/v2015.09.17
Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
#Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
Version is running without Problems so far. Nice Job again. I will monitor if there are Problems with this Version on my End.
September 18, 2015, 05:09:34 PM
New Sling Wallet v2.0.0.1 compiled binaries released for Windows: It can be donwloaded here: https://github.com/CryptoDJ/sling/releases/tag/v2015.09.17
Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
WOW, great work CryptoVote!!
So good to see Sling being developed still.
September 17, 2015, 11:19:12 PM
New Sling Wallet v2.0.0.1 compiled binaries released for Windows: It can be donwloaded here: https://github.com/CryptoDJ/sling/releases/tag/v2015.09.17
Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
Upgrading is NOT required but please test this version and provide feedback. This version fixes bugs and implements new RPC commands for the upcoming market UI I'm developing.
I am planing to release a version in October with the HTML5 UI.
September 16, 2015, 11:06:55 AM
I committed new code to the Sling repo master branch. Version 2.0.0.1 fixes these problems:
https://bitbucket.org/dgslayer/sling/commits/ffe4e24251b28cad85c682aaf2c81051aab3fb2e
- masternode zero fee exploit (see spork.h)
- prevent easy memory exhaustion attack in rpc (see rpcprotocol.cpp)
- priority calculation in CreateTransaction (see wallet.cpp)
- increased the max connections from 8 to 32 (see net.cpp)
https://bitbucket.org/dgslayer/sling/commits/ffe4e24251b28cad85c682aaf2c81051aab3fb2e
nice good job!
You can try commands like marketmylistings, marketalllistings, marketsearchlistings, marketsell, marketbuy....
marketreleaseescrow causes a SegFault so watch out. I need to add more checking before broadcasting to all nodes.
September 15, 2015, 09:45:11 AM
I committed new code to the Sling repo master branch. Version 2.0.0.1 fixes these problems:
https://bitbucket.org/dgslayer/sling/commits/ffe4e24251b28cad85c682aaf2c81051aab3fb2e
- masternode zero fee exploit (see spork.h)
- prevent easy memory exhaustion attack in rpc (see rpcprotocol.cpp)
- priority calculation in CreateTransaction (see wallet.cpp)
- increased the max connections from 8 to 32 (see net.cpp)
https://bitbucket.org/dgslayer/sling/commits/ffe4e24251b28cad85c682aaf2c81051aab3fb2e
September 14, 2015, 09:00:19 PM
Quote
I am still investigating an issue reported with uneven payments for multiple masternodes running on one IP.
Is that the issue I sent you regarding the connection count when having multiple masternodes on the same IP with different ports assigned? If it is, let me know if they is any information you need.
Sending you a PM...
Jump to: