Pages:
Author

Topic: [ANN] [SUMO] SUMOKOIN - 🔏 Digital Cash For Highly-Confidential Transactions 🔏 - page 93. (Read 202439 times)

copper member
Activity: 47
Merit: 0
Hi there!

I develop quality of life bots for crypto discord servers. Give me a shout if you are interested

If you don't already have a Discord server, I can assist in creating and administering the Discord server.

Good luck with this project!
sr. member
Activity: 778
Merit: 252
legendary
Activity: 3108
Merit: 1531
yes
sr. member
Activity: 966
Merit: 359
👉MINING-BIOS.eu💲⛏
They just delete my SUMO suggestion https://nextexchange.featureupvote.com/suggestions/3059/sumokoin-sumo
Did someone request it or they just don't like SUMO or me? :/
newbie
Activity: 3
Merit: 0

Now you got my 2 cents...  Wink
[/quote]

You mean 2 Sats lol
sr. member
Activity: 778
Merit: 252
I'm strongly considering making an investment in SUMOKOIN.

Can anyone tell me what makes you believe in this token?  How will it gain ground against other anonymous cryptos?

Alright... time to shill  Cheesy

First of all: I can't tell why you should invest in Sumokoin. But I can tell why I did. As many people I believe a natural demand of cryptocurrencies exists. After all, that was the core idea of Satoshi Nakamoto: To generate a digital currency that is not controlled by a centralized power AND that is untraceable, just like cash. Of course, most cryptocurrencies state that they offer those two basic features (most of them are decentralized). But only a few are truely untraceable.

Sumokoin truly offers both of those features: With RingCT since day one and a standard mixin of 12, not a single transaction is traceable. The blockchain is private by default (not such bullshit like I2P or TOR with a decrypted blockchain like some other coins who claim to be private...). On top of that is the subaddresses feature, which allows you to recieve funds without reveeling your wallets true address.

Most of those points are valid for xmr as well, but in a weaker way: RingCT was merged late, so most of xmr's old transactions are traceable. Standard mixin is way lower. (Please notice, that I wanted to invest in a low marketcap coin, so xmr was not on my target list).

Besides the tech part: I like the dev, I like the community.  The wallets seem to work way more stable (than xmr's) and I expect great things from dev for 2018.

Now you got my 2 cents...  Wink
full member
Activity: 378
Merit: 102
Code:
2017-Dec-24 15:18:28.330731 [P2P2]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************

2017-Dec-24 17:11:13.153423 [P2P0]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 83786
id:     <9e749b1e64b2a3f7abda76116bc497fd2ffba4e97eb947d89b6c409aabc20ca1>
PoW:   
difficulty:     2110357819
2017-Dec-24 17:18:29.425331 [P2P2]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************

2017-Dec-24 19:18:30.963754 [P2P6]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.

 Huh

Haha, did you even searched for this error in this thread? I posted this last week and @sumogr answered it: https://bitcointalksearch.org/topic/m.26546439
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
Code:
2017-Dec-24 15:18:28.330731 [P2P2]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************

2017-Dec-24 17:11:13.153423 [P2P0]----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 83786
id:     <9e749b1e64b2a3f7abda76116bc497fd2ffba4e97eb947d89b6c409aabc20ca1>
PoW:   
difficulty:     2110357819
2017-Dec-24 17:18:29.425331 [P2P2]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.
**********************************************************************

2017-Dec-24 19:18:30.963754 [P2P6]
**********************************************************************
Last scheduled hard fork time shows a daemon update is needed now.

 Huh
legendary
Activity: 3108
Merit: 1531
yes
This and the question whether there will be - long term - demand for a granite solid privacy coin. Not 80%, not 99% but 100%



Posing the question is answering it. But don’t expect $100 soon. Trust requires time. And time does not come cheap in this field.
member
Activity: 129
Merit: 10
I'm strongly considering making an investment in SUMOKOIN.

Can anyone tell me what makes you believe in this token?  How will it gain ground against other anonymous cryptos?
full member
Activity: 378
Merit: 102
-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.
You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.

Thanks for the tip. I used this on fairpool a while ago, but ms-pool's faq didn't mention they supported this feature.

It's true that with higher network diff, smaller pools are experiencing huge luck issues. Sad
Yep, it's hard. The current Hash Rate of 15+ MH/sec and Difficulty of 3.5G+ are not in favour of small pools.
newbie
Activity: 20
Merit: 0
-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.
You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.

Thanks for the tip. I used this on fairpool a while ago, but ms-pool's faq didn't mention they supported this feature.

It's true that with higher network diff, smaller pools are experiencing huge luck issues. Sad
full member
Activity: 378
Merit: 102
-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.
You can set your diff fixed at the clientside. At least with my pool @ sumo.pandapool.nl (which also suffers bad luck as I mentioned earlier in this thread). Just put the diff behind your wallet address, like: "Sumooxxxxxxxx.100000". This will set your diff to 100K.
full member
Activity: 378
Merit: 102
I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?

Did you compile the wallet on the same machine where you get the segfaults?
Has it ever worked before?

I don't run Sapporo yet, since I don't need subaddresses but the previous version needs following libraries:

ldd sumo-wallet-cli
   linux-vdso.so.1 (0x00007fff7d3f2000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f3068de4000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f3068ae3000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30688c6000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f306851e000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f3068fe8000)

run ldd on your Linux and check if no lib is missing.


No, I didn't compile the wallet on my machine, I downloaded and extracted it. The libs are all there and 'automatic' transfers from my pool are fine, but transferring with cli gives me this error.

Update: I put some extra SUMO in my sending wallet and now the transfer is processed succesfully. Maybe somehow there wasn't enough SUMO in it before, but I would have expected a nice error about this instead of a crash.
newbie
Activity: 34
Merit: 0
I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?

Did you compile the wallet on the same machine where you get the segfaults?
Has it ever worked before?

I don't run Sapporo yet, since I don't need subaddresses but the previous version needs following libraries:

ldd sumo-wallet-cli
   linux-vdso.so.1 (0x00007fff7d3f2000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007f3068de4000)
   libm.so.6 => /lib64/libm.so.6 (0x00007f3068ae3000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f30688c6000)
   libc.so.6 => /lib64/libc.so.6 (0x00007f306851e000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f3068fe8000)

run ldd on your Linux and check if no lib is missing.
full member
Activity: 378
Merit: 102
I try to transfer some Sumo with the sumo-wallet-cli (Sumokoin 'Sapporo' (v0.2.0.0-release)), but every time it crashes with 'Segmentation fault (core dumped)'. I am using the command transfer Sumoo-address-receiver amount.

There is a message that the default mixin 12 is being used and I have to confirm that I don't want to use a payment id. After that it crashes. My wallet has enough unlocked balance, the blockchain is fully synced, so what is going wrong?
newbie
Activity: 20
Merit: 0
-snip-

I see that you use fixed difficulty. For instance, if you start on diff 500, you constantly stay at 500. Other pools have a more dynamic approach. Is there a way I can increase diff manually? My GPU on diff 10000 sends your pool hashes every 6.4 seconds, my CPU on diff 5000 sends every 14.5 seconds... on official pool, my CPU stabilizes around dif 30000 and my GPU around 150000.
sr. member
Activity: 966
Merit: 359
👉MINING-BIOS.eu💲⛏
I found this voting so I add SUMO, this exchange seems little bit strange but I haven't checked it much...
So if devs or community don't agree with listing there I will delete it.

https://nextexchange.featureupvote.com/suggestions/3059/sumokoin-sumo
It still need moderation so it should be active in hours maybe days...
Pages:
Jump to: