Search results

generally yes, though there could be an argument made for having tracking data available to the creator of the link. that is what initially turned me on to bit.ly, i could see where my proposals were getting traction from

i use bit.ly as a url shortener and have never had a link expire going back over 4 years. the only issues i've seen are when forum addresses actually change (happened when the forum url changed from `forum2` to `forum`)

tested this service. it works but the UI leaves something to be desired. status stays at 'waiting' indefinitely, which is concerning.

can you please edit the original post to include the metadata at the top of the post?

please edit the original post to include the metadata code block at the very top of the post.

it is outlined in the pre-proposal guidelines as a pinned post.

quick note: the network only allows proposals up to 6 cycles. beyond that, this is something i've been strongly advocating for since 2017. Buer used to do something similar, but it was usually 'too little too late' in approach, submitting proposals for events that would not pay out until AFTER...

please reformat the original post to include the code block at the start of the post.

please reformat the original post to include the code block at the start of the post.

please reformat the original post to include the code block at the start of the post.

please reformat the original post to include the code block at the start of the post.

Title: Core DevOps Fuzz (Q1 2025) Name: CoreDevOps-Fuzz-Q125 Term: 3 Cycles Cycle Amnt: 15000 PIV Total Amnt: 45000 PIV Author: Fuzzbawls Receiver: Fuzzbawls Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev Created: 2025-01-14 Status: Active Vote Hash...

Title: Core DevOps Fuzz (Q4 2024) Name: CoreDevOps-Fuzz-Q424 Term: 3 Cycles Cycle Amnt: 15000 PIV Total Amnt: 45000 PIV Author: Fuzzbawls Receiver: Fuzzbawls Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev Created: 2024-10-14 Status: Active Vote Hash...

Title: Core DevOps Fuzz (Q3 2024) Name: CoreDevOps-Fuzz-Q324 Term: 3 Cycles Cycle Amnt: 15000 PIV Total Amnt: 45000 PIV Author: Fuzzbawls Receiver: Fuzzbawls Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev Created: 2024-07-13 Status: Active Vote Hash...

Title: Core DevOps Fuzz (Q1 2024) Name: CoreDevOps-Fuzz-Q224 Term: 3 Cycles Cycle Amnt: 15000 PIV Total Amnt: 45000 PIV Author: Fuzzbawls Receiver: Fuzzbawls Address: DBh9o9uRGohcDKpeiEyRiwtmTaTL3xDdev Created: 2024-04-07 Status: Active Vote Hash...

From my perspective, PIVX is already natively available for trade on a wide number of exchanges thanks to the efforts of Jeffery. I am, however, not sure what more can be added via a wrapped token. Liquidity issues above are also a concern with this theoretical idea, and must be accounted for.

somebody here is a surfer...or knows very well a surfer ;)

right now is not the best time to submit this proposal to the network. we're currently approaching the end of a budget cycle, which leaves little time for MNOs to vote on new proposals. Best to wait until a new cycle opens up to give maximum time for voting.

No need to apologize WRT to this. it was my intention/expectation to mentor newcoming devs in the processes and standards that PIVX requires, and all have adapted quite well thus far. I expected initial reluctance and/or confusion regarding this particular point, but through direct and group...

Not true. the now-unused dev discord has only a single user ban, and you are not it.