[ANN] SLING | Fully Working DECENTRALIZED MARKET in Wallet | SLING MARKET LIVE

[CryptoVote]

i would vote for Split Core, since you can leverage full capabilitys of the Browser, with an embedded browser this end up in a Mess.

I agree. It can be difficult to get the embedded browser to recognise all the needed resource files. Also, changing the HTML5 doesn't require a recompile with the split architecture. Any other votes or thoughts before I go this route?

This the the path to sling-html code: https://github.com/CryptoDJ/sling-html
sling-core will compile slingd with the JSON RPC methods needed for the new UI.

[1714656147]

1714656147

[1714656147]

1714656147

[MCDev]

Hello all, how's it going?  Got a question for anyone that may have multiple daemons running on the same VPS.  I've been trying to get this right forever and burned a lot of $$ on VPSes
On the latest VPS, I have 2 instances running, different copies of slingd (slingd001, slingd002) and different datadirs (,SLING001, .SLING002)
On the first instance with port set to 30137, I currently have 28 connections
On the second instance with port set to 30136, 30137, and a bunch of others, I never get over 6 to 7 connections.
I've also tried the same on another VPS with 5 public IPs with the same result, using the different IPs and 30137 but different IPs, and different rpcport

On this last one, I haven't moved the 7331 sling over to start the masternode, I wanted to get the connections up first.
I've also remmed all addnode from the sling.config and deleted the peers.dat, with the same result, 6 - 7 connections

This is what I'm seeing in the debug.log for this particular 2nd node instance.


connect() to 117.104.129.187:30137 failed after select(): Connection refused
SetBestChain: new best= ....
ProcessBlock: ACCEPTED
CDarkSendPool::UpdateState() == 3 | 3
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
SetBestChain: new best=.....
ProcessBlock: ACCEPTED
keypool reserve 1
keypool return 1
SetBestChain: new best=....
ProcessBlock: ACCEPTED
connect() to 193.90.105.180:30137 failed after select(): No route to host
CDarkSendPool::UpdateState() == 3 | 3
connect() to 89.222.233.222:30137 failed after select(): Connection refused
connect() to 108.61.122.121:30137 failed after select(): Connection refused
SetBestChain: new best=....
ProcessBlock: ACCEPTED
CActiveMasternode::ManageStatus() - Checking inbound connection to ....
CActiveMasternode::ManageStatus() - not capable: Wallet is locked.
connected to self at ....., disconnecting
SetBestChain: new best=.....
ProcessBlock: ACCEPTED
SetBestChain: new best=......
ProcessBlock: ACCEPTED
CDarkSendPool::UpdateState() == 3 | 3
SetBestChain: new best=......
ProcessBlock: ACCEPTED


Thanks for any help

[CryptoVote]

Hello all, how's it going?  Got a question for anyone that may have multiple daemons running on the same VPS.  I've been trying to get this right forever and burned a lot of $$ on VPSes
On the latest VPS, I have 2 instances running, different copies of slingd (slingd001, slingd002) and different datadirs (,SLING001, .SLING002)
On the first instance with port set to 30137, I currently have 28 connections
On the second instance with port set to 30136, 30137, and a bunch of others, I never get over 6 to 7 connections.
I've also tried the same on another VPS with 5 public IPs with the same result, using the different IPs and 30137 but different IPs, and different rpcport

On this last one, I haven't moved the 7331 sling over to start the masternode, I wanted to get the connections up first.
I've also remmed all addnode from the sling.config and deleted the peers.dat, with the same result, 6 - 7 connections

This is what I'm seeing in the debug.log for this particular 2nd node instance.


connect() to 117.104.129.187:30137 failed after select(): Connection refused
SetBestChain: new best= ....
ProcessBlock: ACCEPTED
CDarkSendPool::UpdateState() == 3 | 3
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
Successfully synced, asking for Masternode list and payment list
SetBestChain: new best=.....
ProcessBlock: ACCEPTED
keypool reserve 1
keypool return 1
SetBestChain: new best=....
ProcessBlock: ACCEPTED
connect() to 193.90.105.180:30137 failed after select(): No route to host
CDarkSendPool::UpdateState() == 3 | 3
connect() to 89.222.233.222:30137 failed after select(): Connection refused
connect() to 108.61.122.121:30137 failed after select(): Connection refused
SetBestChain: new best=....
ProcessBlock: ACCEPTED
CActiveMasternode::ManageStatus() - Checking inbound connection to ....
CActiveMasternode::ManageStatus() - not capable: Wallet is locked.
connected to self at ....., disconnecting
SetBestChain: new best=.....
ProcessBlock: ACCEPTED
SetBestChain: new best=......
ProcessBlock: ACCEPTED
CDarkSendPool::UpdateState() == 3 | 3
SetBestChain: new best=......
ProcessBlock: ACCEPTED


Thanks for any help

I want to consolidate my masternodes as well. 

By default, Sling is set to 8 maximum connections in net.cpp:

Code:

static const int MAX_OUTBOUND_CONNECTIONS = 8;

Did you increase maxconnections?

[MCDev]

Thanks for the reply,  from sling.conf;

maxconnections=100
rpcuser=myusernames
rpcpassword=mypasswords
rpcallowip=127.0.0.1
rpcport=#####
port=#####

gen=0
server=1
daemon=1
listen=1
staking=0
reservebalance=9999999
masternodeaddr=mypublicip:myport (same as port ##### above)
masternode=1
masternodeprivkey=mykey

Same sling.conf for all nodes, aside from port, rpcport, masternodeaddr, and masternodeprivkey.  Same compiled daemon also, just renamed.

[CryptoVote]

Thanks for the reply,  from sling.conf;

maxconnections=100
rpcuser=myusernames
rpcpassword=mypasswords
rpcallowip=127.0.0.1
rpcport=#####
port=#####

gen=0
server=1
daemon=1
listen=1
staking=0
reservebalance=9999999
masternodeaddr=mypublicip:myport (same as port ##### above)
masternode=1
masternodeprivkey=mykey

Same sling.conf for all nodes, aside from port, rpcport, masternodeaddr, and masternodeprivkey.  Same compiled daemon also, just renamed.

I am trying to replicate.  I'll let you know what I find.

[MCDev]

Thanks...

I am trying to replicate.  I'll let you know what I find.

Easy to tell you program for a living.... Standard term at the office for me 

[CryptoVote]

Bittrex has a de-list warning again...

[jadefalke]

Bittrex has a de-list warning again...

looks like... have already a buy order placed, but people are still holding instead of dumping the Coin's.
Any Progress in Regards to the HTML Wallet?

[CryptoVote]

looks like... have already a buy order placed, but people are still holding instead of dumping the Coin's.
Any Progress in Regards to the HTML Wallet?

I should have the HTML portions of the market UI and more RPC commands it needs completed this weekend. I am going to separate the HTML5 and the core like Twister. There will be a button or link in the Qt wallet that will open the HTML5 market UI.  Eventually, the entire wallet will be HTML5 but I want to release something soon.

Important Masternode Fix Released on Bitbucket.org https://bitbucket.org/dgslayer/sling/commits/ffe4e24251b28cad85c682aaf2c81051aab3fb2e
The payment enforcement date was set to the year 2046 (Linux 2428537599) in Sling's spork.h:

Code:

#define SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT_DEFAULT       2428537599  

I changed it to 10/01/2015 (Linux 1443657600) :

Code:

#define SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT_DEFAULT       1443657600 

I am still investigating an issue reported with uneven payments connections for multiple masternodes running on one IPVPS.

[MCDev]

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...

[CryptoVote]

I committed new code to the Sling repo master branch. Version 2.0.0.1 fixes these problems:

• 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

[CryptoVote]

I committed new code to the Sling repo master branch. Version 2.0.0.1 fixes these problems:

• 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!

Thanks!  I implemented all of the RPC JSON calls needed for the new HTML5 Market UI and committed the code to the master branch on Bitbucket.

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.

[CryptoVote]

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.  

[masyveonk]

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.  

WOW, great work CryptoVote!!

So good to see Sling being developed still.

[jadefalke]

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.  

#

Version is running without Problems so far. Nice Job again. I will monitor if there are Problems with this Version on my End.

[CryptoVote]

WOW, great work CryptoVote!!

So good to see Sling being developed still.

Thanks.  This is fun for me because I am a dork.

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.

[MCDev]

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.

[CryptoVote]

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.

[jadefalke]

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.

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.

[CryptoVote]

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.